Show threadJdeBPAug 18, 2025

@clanger9 @nixCraft

It works *differently* across different operating systems. For starters, on some systems it starts off with the operating system name, on others it starts off with the kernel name.

Try parsing it, in a way that will work across everything from AIX to Ubuntu. It's a nightmare.

One generally ends up with some sort of nested case statement, where one first decides what options to it to use from the result of uname sans options, and then calls it with those options.

#uname

Show threadadacostaJun 23, 2025
@keir Its not too far off from the #uname -v kernel version for #Sequioa which is 24.0. This only tells me the next iPhone is like gonna be iPhone 26.
Diego Córdoba 🇦🇷Jun 10, 2025

Kernel Linux v6.15.1 en #ArchLinux... y al reiniciar, misteriosamente, no se rompió el driver de la #nvidia y pude entrar a #x11 a la primera 😅

#linux #kernel #uname #gnu #arch

Show threadFelix Palmen  Feb 27, 2025

@ax6761 Well, you could call it an implementation glitch. #uname is *meant* to give you information about "the OS", but has always been implemented as a #syscall (dating back to early Unix versions), therefore actually tells you something about the #kernel.

In #FreeBSD, the kernel doesn't *have* to be the exact same version as the userland, and for security updates, a new kernel is only built when some patch actually affects the kernel.

Note that on a #Linux system, it's arguably even "worse", as Linux is nothing but the kernel. To know version information about the rest of your installed OS, you'll have to use distribution specific information (or more recently look at the now standardized /etc/osrelease).

Dendrobatus AzureusFeb 15, 2025

A few tooters have asked me what my config is, at which I replied that I run the Fediverse, platform agnostic. Then one asked what one of my main horizontal display systems run, at which I now reply with

` uname -a`
{Linux devakprata 6.12.13-2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.12-18~mx23ahs (2025-02-10) x86_64 GNU/Linux}

**Note**
I left the results of

`cat /proc/cpuinfo` out since I would get that 16 times!!!

` cat /proc/meminfo `
{MemTotal: 31750332 kB
MemFree: 27996612 kB
MemAvailable: 29376500 kB
Buffers: 85900 kB
Cached: 1890756 kB
SwapCached: 0 kB
Active: 2357024 kB
Inactive: 892372 kB
Active(anon): 1546640 kB
Inactive(anon): 0 kB
Active(file): 810384 kB
Inactive(file): 892372 kB
Unevictable: 48 kB
Mlocked: 48 kB
SwapTotal: 6291452 kB
SwapFree: 6291452 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 156 kB
Writeback: 0 kB
AnonPages: 1273116 kB
Mapped: 719588 kB
Shmem: 273900 kB
KReclaimable: 67860 kB
Slab: 169900 kB
SReclaimable: 67860 kB
SUnreclaim: 102040 kB
KernelStack: 16160 kB
PageTables: 30512 kB
SecPageTables: 4112 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 22166616 kB
Committed_AS: 6017728 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 98420 kB
VmallocChunk: 0 kB
Percpu: 7680 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
CmaTotal: 0 kB
CmaFree: 0 kB
Unaccepted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 347964 kB
DirectMap2M: 7952384 kB
DirectMap1G: 24117248 kB}

and this screencap

#neofetch #sysinfo #POSIX #uname #Linux #Fediverse #federated #OpenSource #hardware #AMD #AMD64

 Qiita - 人気の記事Feb 1, 2025

個人的な備忘録：Linuxに入ったら打つべき3つのコマンドを記事としてアウトプットしてみた
https://qiita.com/free-honda/items/ba6e80dc224fb6fcf1b4?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Linux #SSH #コマンド #pwd #uname

個人的な備忘録：Linuxに入ったら打つべき3つのコマンドを記事としてアウトプットしてみた - Qiita

はじめに私自身、サーバーの運用や保守に携わる中で、LinuxサーバーにSSH接続した際に必ず実行すべき3つのコマンドがありました。今回は、それらのコマンドについて実際に手を動かしながら解説し、記…

Qiita
НайменшенькийJun 17, 2024

Ну чому не можна було дати тільки одну назву для одної архітектури. У процесорів для настільних ПК є 32-bit й 64-bit архітектур які називаються, або x86 і x86_64, або i386 і amd64 відповідно. А ще іноді 32-bit називають i686.

Проблема ж у, тому що у різних місцях може прийматись тільки один варіант і важко запамʼятати де який.

Для прикладу у репозиторіях Arch GNU/Linux пакунки мають мітку x86_64 архітектуру, а у Debina GNU/Linux - amd64.

Перевірити архітектуру в терміналі можна кількома способами.

  • Uname
    • $ uname -m x86_64
  • dpkg (debian)
    • $ dpkg --print-architecture amd64

    #процесори #архітектури #cpu #processors #arch #architecture #x86 #i386 #i686 #x86_64 #amd64 #uname #dpkg #repos #linux

    Social.Net.Ua

    Sven GeggusJan 16, 2024
    Wie kann ich denn den string x86_64-linux-gnu erzeugen? Also so dass der zum Beispiel auf nem Pi arm-linux-gnueabihf ist? Mit #uname scheitere ich gerade.
    alipAug 1, 2021
    Here is the specs of the #Gentoo box kindly hosting https://caissa.ai, https://lichess.org/@/caissaai/tv: #uname: https://dev.exherbo.org/~alip/images/caissa-ai-uname.png #rescue: https://dev.exherbo.org/~alip/images/caissa-ai-rescue.png (thank you #hetzner!), #mutterboard: https://dev.exherbo.org/~alip/images/caissa-ai-mutterboard.png #motherboard #motherboard-awards: https://dev.exherbo.org/~alip/images/caissa-ai-mutterboard-awards.png #Freedom #Chess #HastaLaVictoriaSiempre #Venceremos #serfirazkin
    TzafrirMay 12, 2020

    We have a bunch of build scripts to build kernel-related stuff that have to run in a VM. Why not move them to containers?

    One component: move /usr/bin/uname aside and replace it with:

    #!/bin/sh
    UNAME_REAL="/usr/bin/uname-real"
    RELEASE_WANTED="4.20-whatever"
    release=`$UNAME_REAL -r`
    output=`$UNAME_REAL "$@"`
    rc=$?
    echo "$output" | sed -e "s/$release/$RELEASE_WANTED/"
    exit $rc

    # #uname #linux #kernel