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.
OK, just done some R&D into a Slackware based roll-out. Clonezilla is a good contender. It seems to sort out the udev id issue for you (by default, you can turn it off). What I recommend to anyone doing this is to keep the partitions to smallest sizes you're gonna install to. Clonezilla can resize partitions bigger but not smaller. I used gparted in a livecd to shrink the existing installation before imaging. But it wuold be better to install it this way initially.
Another way I'm thinking of doing it is a script that pull in my packages and settings and essentially sets everything up automagically. So the end result would be to install vanilla slack, then run a script which would wget to update itself and pull everything from a sort of repo and perhaps database. This way is more flexible and allows for centrally managed changes over time. However, it will probably be more work initially.
In my previous roll-out I used livecd generating tools to remaster an installabel ISO. It was cool but the remastering is slow (not a big deal) and the development cycle required lot's of re-installing.
Either way, what I've learnt is to put everything in packages. Not only is it easier to distribute and update, it's easier to track the customisations.