![]() 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. Please create it first, and then re-run this script. Target directory /home/ftp/pub/Linux/Slackware/slackware-13.37/patches does not exist! Syncing patches for slackware version '13.37'. # /usr/local/bin/rsync_slackware_patches.sh Simply run the script once, and see what it reports: The script uses a couple of defaults which you may want to change to suit your environment - such as the location where the script will download the patches to. # chmod +x /usr/local/bin/rsync_slackware_patches.sh You download the script, edit it to use your favorite mirror server and make it executable so that it can be used in a cron job: # wget -O /usr/local/bin/rsync_slackware_patches.sh And of course, have a script that does the work.Īn example of such a script is rsync_slackware_patches.sh which watches the Slackware ChangeLog.txt for updates. Again, see the slackpkg page for guidelines about the use of this tool.Īnother way is to setup a script to check for updates once a day and make the script email you when updates are available.įor this to work you need to have sendmail configured (although it usually runs out of the box) and know how to create a cron job. After updating the database you can let it download and install the updates. You will need to update the slackpkg database from time to time, when you learn about the availability of new patches for your distribution. Note that package management is done as the “ root” user! When you have done that, you need to initialize slackpkg's database by running Make sure that the URL mentions the release number for the version of Slackware you are running! Also, pick a mirror which is close to you or of which you know it is fast. Open the file in a text editor such as nano or vi and uncomment a single mirror URL. Before you can use slackpkg you will need to define an online mirror from which it will download updates to your computer.Ī list of available mirrors for your Slackware version can be found in this file: ![]() Your best option is to use slackpkg, which is a package manager on top of Slackware's own pkgtools. There is a lot that you can do with Slackware! Let's start with the basics. After that, it is time to start considering the installation of “ Proprietary Graphics Drivers” (if you own a Nvidia or Ati card), setting up a wireless network connection or starting a graphical desktop environment. The first thing to do is create a fresh user account for yourself, without the root privileges. Root is meant for system maintenance and configuration, software upgrades and the like. So now what? The “ root” user is not the account which you are going to use as a matter of routine. Login as “root” now - you will find yourself at a “ #” console root-prompt. You should remember the root password, which you set at the very end of the installation procedure. At this stage, there is only the “ root” account. The installation did not offer to create a user account. It is the first stage in a learning experience which will make you a lot more knowledgeable in Linux after as little as a few weeks. When Slackware starts for the first time after completing the installation and rebooting, you will notice that it boots to a console log in screen - not the graphical login screen you may expect from using other distributions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |