Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
slackware:beginners_guide [2012/09/26 01:59 (UTC)] – [Post Installation Overview] updated internal link mfillpot | slackware:beginners_guide [2015/12/07 12:46 (UTC)] – [Make Slackware Speak your Language] Capital letters for "English" sycamorex |
---|
# useradd -m -g users -G wheel,floppy,audio,video,cdrom,plugdev,power,netdev,lp,scanner -s /bin/bash slacker | # useradd -m -g users -G wheel,floppy,audio,video,cdrom,plugdev,power,netdev,lp,scanner -s /bin/bash slacker |
</code> Once that’s done you can log in to your user account. \\ Log out of the root account (type ''logout'' at the root prompt) and then login using the new account you just created. Now come the really interesting adventures! | </code> Once that’s done you can log in to your user account. \\ Log out of the root account (type ''logout'' at the root prompt) and then login using the new account you just created. Now come the really interesting adventures! |
| |
| |
| ===== Make Slackware Speak your Language ===== |
| |
| Slackware's installer is English-only and it will also assume that English is the language in which you want to be addressed by the programs on your computer. If you are a non-English speaker and want your Slackware system to "talk" to you in your own language, you should check out our instruction article "[[slackware:localization|Localization: Adapt Slackware to your own Language]]" |
| |
| |
[rsync_slackware_patches.sh:] Please create it first, and then re-run this script. | [rsync_slackware_patches.sh:] Please create it first, and then re-run this script. |
</code> \\ You notice that you will have to edit the script and define a local directory (//and create that directory too!//) for the script to use. When that is done, you should run the script once - for a first-time download of patches. \\ Then you can use cron to run the script once a day. For instance, schedule the script to run at 05:33 every day, and let it check for updates to the 64-bit version of Slackware-13.37. Open the crontab editor by typing <code>crontab -e</code> and then you add the following line to your cron table: <code> | </code> \\ You notice that you will have to edit the script and define a local directory (//and create that directory too!//) for the script to use. When that is done, you should run the script once - for a first-time download of patches. \\ Then you can use cron to run the script once a day. For instance, schedule the script to run at 05:33 every day, and let it check for updates to the 64-bit version of Slackware-13.37. Open the crontab editor by typing <code>crontab -e</code> and then you add the following line to your cron table: <code> |
33 5 * * * /usr/local/sbin/rsync_slackware_patches.sh -q -r 13.37 -a x86_64 | 33 5 * * * /usr/local/bin/rsync_slackware_patches.sh -q -r 13.37 -a x86_64 |
</code> This command will be executed silently (meaning you will not get emailed) if no new patches are found. However when the script finds updates it will download them and email you the script's output. You will get an email like this: <code> | </code> This command will be executed silently (meaning you will not get emailed) if no new patches are found. However when the script finds updates it will download them and email you the script's output. You will get an email like this: <code> |
[rsync_slackware_patches.sh:] New patches have arrived for Slackware 13.37 (x86_64)! | [rsync_slackware_patches.sh:] New patches have arrived for Slackware 13.37 (x86_64)! |