Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howtos:misc:get_acquainted_with_slackware [2015/01/25 21:28 (UTC)]
didierspaier [Management of software packages]
howtos:misc:get_acquainted_with_slackware [2016/04/30 23:24 (UTC)] (current)
zithro [Management of software packages] minor typos
Line 4: Line 4:
 This document is intended to allow people who have already used another "​Unix-like"​ system to get quickly acquainted with This document is intended to allow people who have already used another "​Unix-like"​ system to get quickly acquainted with
 Slackware. We assume that the reader: Slackware. We assume that the reader:
-  * know the main Unix commands and the associated concepts, +  * knows the main Unix commands and the associated concepts, 
-  * know how-to edit a text file (such as a configuration file)+  * knows how-to edit a text file (such as a configuration file)
   * can read a simple shell script.   * can read a simple shell script.
  
Line 36: Line 36:
 |-- pasture/ ​             obsolete packages and sources |-- pasture/ ​             obsolete packages and sources
 |-- patches/ ​             packages and sources updated after a release |-- patches/ ​             packages and sources updated after a release
-|-- slackware/ ​           base packages (if 64-bit) +|-- slackware/ ​           base packages (if 32-bit) 
-|-- slackware64/ ​         base packages (if 32-bit)+|-- slackware64/ ​         base packages (if 64-bit)
 |-- testing/ ​             packages intended for adventurous |-- testing/ ​             packages intended for adventurous
 `-- usb-and-pxe-installers/​ alternate installation methods `-- usb-and-pxe-installers/​ alternate installation methods
Line 78: Line 78:
 [[http://​slint.fr|Slint]] offers [[http://​slint.fr/​installer.html|polyglot [[http://​slint.fr|Slint]] offers [[http://​slint.fr/​installer.html|polyglot
 installers]],​ which also complement the system configuration:​ choosing the installers]],​ which also complement the system configuration:​ choosing the
-language, keyboard ​amp and creating ordinary users. A+language, ​the keyboard ​layout ​and creating ordinary users. A
 [[http://​slint.fr/​package.html|Slint package]], also installed, provides [[http://​slint.fr/​package.html|Slint package]], also installed, provides
 polyglot versions of the main administration tools and/or their manual polyglot versions of the main administration tools and/or their manual
Line 93: Line 93:
   * To change the font for the console type ''​setconsolefont''​   * To change the font for the console type ''​setconsolefont''​
   * To change the console keymap edit /​etc/​rc.d/​rc.keymap and make it executable   * To change the console keymap edit /​etc/​rc.d/​rc.keymap and make it executable
-  * To change the LANG edit /​etc/​profile.d/​lang.sh and case occuring ​/​etc/​profile.d/​lang.csh. Note: in Slackware /bin/sh is a symlink to /​bin/​bash. +  * To change the LANG edit /​etc/​profile.d/​lang.sh and case occurring ​/​etc/​profile.d/​lang.csh. Note: in Slackware /bin/sh is a symlink to /​bin/​bash. 
-  * To modify the keyboard settings for X (in graphical mode), copy usr/​share/​X11/​xorg.conf.d/​90-keyboard-layout.conf to /​etc/​X11/​xorg.conf.d,​ hen edit the copy. The file /​etc/​X11/​xkb/​rules/​evdev.lst lists all known alues for XkbModel, XkbLayout, XkbVariant and XkbOptions under the especive ​headings ''​! model'',​ ''​! layout'',​ ''​! variant''​ and ''​! option''​+  * To modify the keyboard settings for X (in graphical mode), copy usr/​share/​X11/​xorg.conf.d/​90-keyboard-layout.conf to /​etc/​X11/​xorg.conf.d,​ hen edit the copy. The file /​etc/​X11/​xkb/​rules/​evdev.lst lists all known alues for XkbModel, XkbLayout, XkbVariant and XkbOptions under the respective ​headings ''​! model'',​ ''​! layout'',​ ''​! variant''​ and ''​! option''​
   * You can re-run the setup scripts (already used at the end of installation) using the command ''​pkgtool'',​ menu entry ''​Setup''​.   * You can re-run the setup scripts (already used at the end of installation) using the command ''​pkgtool'',​ menu entry ''​Setup''​.
  
Line 103: Line 103:
 In general, Slackware does not prejudge how the system will be used. It is up In general, Slackware does not prejudge how the system will be used. It is up
 to the administrator to customize it for its intended usage by editing the to the administrator to customize it for its intended usage by editing the
-configuration files located in /etc or its subdirectoriesReading ​comments+configuration files located in /etc or its sub-directoriesIt helps to read the comments
 in scripts for management of services located in /etc/rc.d as well as in the in scripts for management of services located in /etc/rc.d as well as in the
-configuration files helps.+configuration files.
  
 === Startup === === Startup ===
Line 147: Line 147:
   * using the command ''​pkgtool''​ (choose ''​Setup''​ then ''​services''​ in the menu).   * using the command ''​pkgtool''​ (choose ''​Setup''​ then ''​services''​ in the menu).
  
-Note. As all administration tools, ''​pkgtools''​ should be run as root.+Note. As all administration tools, ''​pkgtool''​ should be run as root.
  
 ==== Management of software packages ==== ==== Management of software packages ====
Line 164: Line 164:
 usually ends with the execution of the ''​makepkg''​ command, which makes the usually ends with the execution of the ''​makepkg''​ command, which makes the
 archive from the package'​s file tree, including case occuring the archive from the package'​s file tree, including case occuring the
-appropriate installation scripts, cf. "man makepkg."+appropriate installation scripts, cf. "man makepkg"​.
  
 The software packages are in the directories of installation media indicated The software packages are in the directories of installation media indicated
Line 309: Line 309:
 elsewhere. Important warnings: elsewhere. Important warnings:
   * Know who proposes these packages and preferably trust contributors of Slackware or at least of http://​slackbuilds.org   * Know who proposes these packages and preferably trust contributors of Slackware or at least of http://​slackbuilds.org
-  * Carefully inspect the contents of packages before installation,​ including a check  of the permissions of files and any changes to existing directories and files. Use ''​less'',​ ''​tar''​ and/or ''​explodepkg'',​ see "man explodepkg."+  * Carefully inspect the contents of packages before installation,​ including a check  of the permissions of files and any changes to existing directories and files. Use ''​less'',​ ''​tar''​ and/or ''​explodepkg'',​ see "man explodepkg"​.
   * Never install a package whose sources and SlackBuild are not available.   * Never install a package whose sources and SlackBuild are not available.
  
Line 316: Line 316:
 to directories containing "​unofficial"​ Slackware packages. to directories containing "​unofficial"​ Slackware packages.
  
-=== Build you own packages ===+=== Build your own packages ===
  
 This is the recommended method if no SlackBuild is available, to benefit of This is the recommended method if no SlackBuild is available, to benefit of
Line 322: Line 322:
  
 The software ''​slacktrack'',​ included in Slackware, can help you, as "man The software ''​slacktrack'',​ included in Slackware, can help you, as "man
-makepkg." Inspecting existing Slackbuilds and+makepkg"​Inspecting existing Slackbuilds and
 [[http://​slackbuilds.org/​templates/​|templates]] proposed at slackbuilds.org can [[http://​slackbuilds.org/​templates/​|templates]] proposed at slackbuilds.org can
 inspire you. Browse [[http://​docs.slackware.com|SlackDocs]] with the key word inspire you. Browse [[http://​docs.slackware.com|SlackDocs]] with the key word

In Other Languages
QR Code
QR Code howtos:misc:get_acquainted_with_slackware (generated for current page)