YAST(8)

πŸ“¦ version 5.0.13, in opensuse-leap 16.0

πŸ’… YAST(8) β€” like, the whole entire manual page, bestie

okay so this is the yast page from section 8 of the manual (yeah, the system configuration one β€” YAST(8), iykyk) and I'm gonna walk you through it like we're texting at 2am 🫢


✨ NAME ✨

YaST β€” "Yet another Setup Tool", the installation and configuration tool 🌸


✨ SYNOPSIS ✨

yast2 [ options ] [ module ] [ module specific options ]

like, options first, then a module, then that module's own options. in that order, bestie πŸ’…


✨ DESCRIPTION ✨

So YaST is literally the tool for configuring your system. It can configure common hardware (sound cards, printers πŸ–¨οΈ), network connections (network cards), network clients and services (like NFS, FTP), and also general system options (language, partitioning, software, bootloader). it's giving main character energy for your whole system ngl πŸ‘‘

YaST comes with Qt (graphical) and ncurses (text mode) frontends, which live in the libyui-qt and libyui-ncurses packages. Both frontends are functionally equivalent β€” no cap, they do the same stuff. The correct frontend gets selected automatically based on the available components and the current environment (the DISPLAY variable). so it just knows. obsessed ✨

Use yast2 alone to launch the YaST Control Center, where you can pick a particular configuration module β€” or use yast2 module to launch the module directly. shortcuts, we love them πŸŽ€


✨ OPTIONS ✨

  • --qt β€” run YaST in the Qt graphical frontend if it's available, otherwise it uses the ncurses frontend. (bestie said "graphical if we can, text if we must" πŸ’…)
  • --ncurses β€” run YaST in the ncurses text mode frontend πŸ–₯️
  • -g, --geometry β€” default window size (Qt frontend only), e.g. 800x600
  • -h, --help β€” print usage and exit πŸ‘‹
  • -l, --list β€” list all available modules. to obtain usage info about a module, use the yast module help command πŸ—’οΈ

✨ COMMAND LINE INTERFACE ✨

Some YaST modules support a command line interface. (not all of them, so don't come for me πŸ™ˆ)

To obtain a list of basic commands for using a YaST module with support for command line interface, use:

yast2 module help

To get more comprehensive information about the commands available for a YaST module, use:

yast2 module longhelp

To get information about the commands available for a YaST module in a XML formatted file, use:

yast2 module xmlhelp xmlfile=<filename>

To get information about a specific command of a YaST module, use:

yast2 module command help

To start an interactive console in which you can execute commands of a YaST module, use:

yast2 module interactive

literally a whole lil REPL for your modules, slay πŸšπŸ’œ


✨ FILES ✨

  • /var/log/YaST2/* β€” log files. use the save_y2logs command for saving all files into a single archive πŸ“¦ (so handy fr fr)
  • /etc/sysconfig/yast2, $HOME/.yast2/yast2 β€” YaST configuration files πŸ—‚οΈ

✨ EXIT STATUS ✨

  • 0 β€” successful program execution πŸŽ‰
  • 1 β€” too few arguments 😭
  • 5 β€” error in arguments πŸ’€
  • 16 β€” generic module error
  • > 16 β€” module specific error codes
so like, if you get something bigger than 16, that's the module being dramatic on its own terms. check the module docs, bestie 🫢

✨ AUTHOR ✨

The YaST Team <yast-devel@opensuse.org> πŸ’Œ


✨ SEE ALSO ✨

Documentation in /usr/share/doc/packages/yast2*. go read it, it's giving lore πŸ“šβ­


okay that's the whole page, no cap, nothing skipped πŸ’– this was yast β€” from April 2021, page YAST(8) of the manual β€” and honestly? iconic. periodt. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from