Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:handbook:systemutils [2016/11/27 16:39] hgt crontab -e works on SliTaz also |
en:handbook:systemutils [2022/08/04 12:20] hgt updated some versions for SliTaz 5 |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Devices and disk access ===== | ===== Devices and disk access ===== | ||
| - | With Linux your disks and USB media are seen as devices. To access them you must first mount a device on a mount point (directory). On SliTaz you can graphically mount devices by using mountbox or the command line. To mount the first disk of a local hard disk on ///mnt/disk//: | + | With Linux disks and USB media are seen as devices. To access data on them, a device first must be mounted on a mount point (directory). |
| + | |||
| + | On SliTaz devices can be mounted using a program with a graphical user interface, like ''pcmanfm'' or with a command from a terminal. | ||
| + | |||
| + | To mount the first partition of a local disk on ''/mnt/disk'': | ||
| <code> | <code> | ||
| # mkdir -p /mnt/disk | # mkdir -p /mnt/disk | ||
| - | # mount /dev/hda1 /mnt/disk | + | # mount /dev/sda1 /mnt/disk |
| </code> | </code> | ||
| - | To mount a cdrom or an USB media you should use mount points located in ///media//. Note that for a cdrom, you just have to specify the device path. For a flash key, the mount point already exists: | + | To mount an optical disk or an USB medium, mount points located in ''/media'' should be used. |
| + | |||
| + | Note that for an optical disk, you just have to specify the device path. For a flash key, the mount point already exists: | ||
| <code> | <code> | ||
| Line 19: | Line 25: | ||
| === NTFS filesystem === | === NTFS filesystem === | ||
| - | If you need read/write access to Windows ntfs filesystems you must install a few additional packages from the mirror. The ntfs-3g driver provides stable access to ntfs partitions and ntfsprogs provides manipulation tools dependent on fuse. Note that you can format, move or resize ntfs partitions graphically with Gparted. | + | If read or write access to Windows ntfs filesystems is needed, a few additional packages from the repository must be installed. |
| + | |||
| + | The ''ntfs-3g'' driver provides stable access to ntfs partitions and ''ntfsprogs'' provides manipulation tools dependent on fuse. | ||
| + | Note that ntfs partitions can be formatted, moved or resized using Gparted, a GUI to parted. | ||
| === NFS === | === NFS === | ||
| - | NFS (Network File System) is the native unix/linux method for sharing file systems. In this respect its function is similar to samba. The most popular version is still NFSv3 which is able to use either UDP or TCP as the network protocol. The older NFSv2 was only capable of using UDP. On a local LAN, UDP is still the fastest protocol; TCP is to be preferred when the machines are connected over a WAN. | + | NFS (Network File System) is the native UNIX and Linux method for sharing file systems. |
| + | In this respect its function is similar to Samba. | ||
| + | |||
| + | The most popular version is still NFSv3, which is able to use UDP or TCP as the network protocol. | ||
| + | |||
| + | The older NFSv2 was only capable of using UDP. | ||
| + | |||
| + | On a LAN, UDP is still the fastest protocol; TCP is to be preferred when the machines are connected over a WAN. | ||
| NFSv3 has been superseded by NFS version4 which has notable improvements (security) over v3 but its configuration has become a lot more complex as a result. | NFSv3 has been superseded by NFS version4 which has notable improvements (security) over v3 but its configuration has become a lot more complex as a result. | ||
| - | An NFS server exports a part of it's file system; i.e. makes it available on the network. The server is configured with details about client ip addresses or host names and can restrict their access to the file system. Access can be read-only, read-write or no access at all. | + | An NFS server exports a part of it's file system; i.e. makes it available on the network. |
| + | The server is configured with details about client ip addresses or host names and can restrict their access to the file system. | ||
| + | Access can be read-only, read-write or no access at all. | ||
| An NFS client simply mounts the exported file systems as if they were local devices. | An NFS client simply mounts the exported file systems as if they were local devices. | ||
| - | The NFS software in Slitaz makes it possible to run both as a server or a client. To start the NFS processes, you need to run the init script in etc/init.d/. | + | The NFS software in Slitaz makes it possible to run both as a server or a client. |
| - | <code>/etc/init.d/nfsd start|stop</code> | + | To start the NFS processes, you need to run the init script in ''/etc/init.d/'': |
| + | <code>/etc/init.d/nfsd start|stop|restart</code> | ||
| <note tip>The NFS daemons must be running also when the machine acts as a client.</note> | <note tip>The NFS daemons must be running also when the machine acts as a client.</note> | ||
| Line 37: | Line 57: | ||
| <code> | <code> | ||
| # tazpkg -l | grep nfs | # tazpkg -l | grep nfs | ||
| - | linux-nfsd 2.6.37 base-system | + | linux-nfsd 3.16.55 base-system |
| - | nfs-utils 1.2.2 system-tools | + | nfs-utils 2.6.1 system-tools |
| </code> | </code> | ||
| Line 62: | Line 82: | ||
| /usb1 192.168.1.0/24(rw,sync,no_subtree_check) | /usb1 192.168.1.0/24(rw,sync,no_subtree_check) | ||
| </code> | </code> | ||
| - | The server is only exporting one drive: usb1. Clients must be in the 192.168.1.0/24 network and they have read-write access. | + | The server is only exporting one filesystem: usb1. Clients must be in the 192.168.1.0/24 network and they have read-write access. |
| To use nfs on the client; all you need to do is start nfsd and mount the share: | To use nfs on the client; all you need to do is start nfsd and mount the share: | ||
| <code> | <code> | ||
| # /etc/init.d/nfsd start | # /etc/init.d/nfsd start | ||
| + | # mkdir /mnt/usbdrive1 | ||
| # mount server:/usb1 /mnt/usbdrive1 | # mount server:/usb1 /mnt/usbdrive1 | ||
| </code> | </code> | ||
| - | Please note the specific format for nfs shares **servername** colon slash-mountpoint**. | + | Please note the specific format for nfs shares ''//server//'':''//mountpoint//''. |
| - | Naturally you must also make sure that the specified mount point (directory) exists on the client. | + | |
| ===== Users, groups and passwords ===== | ===== Users, groups and passwords ===== | ||
| Line 82: | Line 102: | ||
| - | === Manipulating users & group membership: === | + | === Manipulating users and group membership === |
| - | Linux groups are a mechanism to manage a collection of computer system users. All Linux users have a user ID and a group ID and a unique numerical identification number called a userid (UID) and a groupid (GID) respectively. Groups can be assigned to logically tie users together for a common security, privilege and access purpose. It is the foundation of Linux security and access. Access to files and devices may be granted based on a user ID or a group ID. This mechanism is the same for all of linux but the way it is configured varies per distribution. Sometimes additional or different commands are used, like for example usermod, chgrp, useradd or groupadd. Below is an overview of how to handle users, groups and group membership on Slitaz. | + | Linux groups are a mechanism to manage a collection of computer system users. |
| + | All Linux users have a user name and a group name and a unique numerical identification number called a userid (UID) and a groupid (GID) respectively. | ||
| + | Groups can be assigned to logically tie users together for a common security, privilege and access purpose. | ||
| + | It is the foundation of Linux security and access. | ||
| + | Access to files and devices may be granted based on a userid or a groupid. | ||
| + | This mechanism is the same for all of linux but the way it is configured varies per distribution. | ||
| + | Sometimes additional or different commands are used, like for example ''usermod'', ''chgrp'', ''useradd'' or ''groupadd''. | ||
| + | Below is an overview of how to handle users, groups and group membership on Slitaz. | ||
| - | The Slitaz way is using only four commands. Simple & Elegant. ;-) | + | The Slitaz way is using only four commands. Simple and Elegant. ;-) |
| <code> | <code> | ||
| Line 104: | Line 131: | ||
| </code> | </code> | ||
| - | Any user can be member of any group and the combination of user & group permissions allows for granular access to system resources. | + | Any user can be member of any group and the combination of user and group permissions allows for granular access to system resources. |
| === Passwd === | === Passwd === | ||
| Line 120: | Line 147: | ||
| ===== Language and keyboard layout ===== | ===== Language and keyboard layout ===== | ||
| - | SliTaz saves the configuration of the default locale in ///etc/locale.conf// which is read by ///etc/profile// on each login and the keyboard setting is stored in ///etc/kmap.conf//. These two files can be edited with your favorite editor or configured respectively with //tazlocale// and //tazkeymap//. You can modify the settings you chose on the first boot by typing as root administrator: | + | SliTaz saves the configuration of the default locale in ///etc/locale.conf// which is read by ///etc/profile// on each login and the keyboard setting is stored in ///etc/keymap.conf//. These two files can be edited with your favorite editor or configured respectively with //tazlocale// and //tazkeymap//. You can modify the settings you chose on the first boot by typing as root administrator: |
| <code> # tazlocale | <code> # tazlocale | ||
| Line 135: | Line 162: | ||
| ===== Custom SHell ===== | ===== Custom SHell ===== | ||
| - | SliTaz uses the ash shell linked to sh provided by busybox. Ash is light, fast and standards compliant. To change the default shell for a user you can edit the /etc/passwd file using the corresponding line. After you login, /etc/profile is read first and then the user file ~/profile. You can edit these files with a text editor to configure the language, any aliases, etc. | + | SliTaz uses the ash shell linked to sh provided by busybox. Ash is light, fast and standards compliant. To change the default shell for a user you can edit the /etc/passwd file using the corresponding line. After you login, /etc/profile is read first and then the user file ~/.profile. You can edit these files with a text editor to configure the language, any aliases, etc. |
| === Example: ~/.profile === | === Example: ~/.profile === | ||