SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How easy or difficult would it be to have a progress bar (like in swaret or even, i think wget), so we would know it is actually doing something, or stalled?
Reason why I ask is my internet cut out in a storm and the script was still running on a different terminal. I restored the connection for the os, but the script stayed at the same place for the next two days (My bad. I forgot it was running on a different terminal)
on Server2 and/or Server3 ? Lots of disk space wasted if you ask me, one copy would be enough and you have NFS?
Not sure if I agree. I'd like to keep a complete copy of the official mirror's slackware and slackware-current directories on my main server. This to be able to use your script to burn a current-iso at any time, and at the same time have the stable also handy.
Then, for the end-user laptops and desktops, I'd like to have only -current stored locally in the /root directory, so that it's relatively easy to do an upgradepkg whenever something interesting shows up in Pat's -current. One gigabyte give or take means nothing on relatively modern systems, at least not to me.
Thus it'd be great to have a script that on the server syncs _everything_, but on the various PCs skip KDEI, kernels, aaa* and others which I wouldn't want to use with upgradepkg --installnew */*.tgz anyway.
Eric, will this create a 10.2 release DVD ISO or a 10.2 with all of the updates DVD ISO? Just curious.
The DVD ISO you create with the script will contain everything in the slackware-10.2 tree. That includes the /patches directory i.e. all updates to Slackware 10.2 will be available on the DVD for post-installation.