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.
You misunderstand: the ubuntu remastering was an example. I guessed that, as a slack hacker, you'd have the skills to extrapolate from this. Apparently I was mistaken. I apologise.
basic remastering is always the same: ... for a general iso, you mount it, move the content to a working directory, modify whatever you want in the working directory (unmount the iso - you don't need it any more), then create a new iso from the modified files.
... these concern remastering the slackware distro iso's. If you have a different iso, there will not be any information explicitly for you. You will have to extrapolate from these examples the kind of thing you want. Please let me know if you find this too difficult.
I gave you the ubuntu one as a kickoff because it contains a lot of the ideas you need to get started, and it is easy to read. Combined with your slackware experience, this should have been sufficient. I misjudged the situation - please excuse me.
I need some kind of program to manipulate iso's: Read the files, change them if needed, add/remove programs, etc.
I don't think this is exactly what you were looking for, but what about using QEMU to test the iso before burning it? You'd still have to do the changes to your working directory and then remake the iso, but at least you would cut down on coasters.
Distribution: Slackware & Slamd64. What else is there?
I think what CW's asking for is a pretty standard need. I haven't checked through the links in the thread yet but for example, OpenBSD doesn't supply distribution ISOs online. The only ISOs they have on their sites are bootable images that contain just the kernel, some drivers, installation scripts, shell, etc. When you install OpenBSD from the ftp sites you download and burn the ISO boot image and then start ftping all the packages. You can also download the packages, but there isn't a convenient way to add all this stuff to the bootable image and make a nice ISO. This is a good of an example of what I think he's asking for (and I would be interested in also).
P.S. Don't flame CW as he is one of the nice and helpful guys (actually, all the Slackers are).
Just about dead on Randux. What I'm EXACTLY doing is making iso's of slackware-current. But what I want to do is have the option of booting my custom 2.6.17-rc3 kernel from the get go. (Kinda like doing test26.s), along with the associated source and modules. The only way I've been able to do it is to add some kludgy lines in the script to copy the customized files over, then it proceeds to make the iso.
What I'd like to do is manipulate the files after they've been "iso'd", so if I need to tweak a file here or there, I can do it without going through the whole process.
I know Windows has a few programs out there that allow you to do exactly that, and I was wondering if there are any Linux ones that do the same.
The whole deal is purely a intellectual issue for me at this point (How many people have the exact same hardware I do?), but it's gotten to the point of obsession....Seems so easy, but.....
Last edited by cwwilson721; 05-16-2006 at 11:17 AM.
Actually I don't think you can modify ISOs directly. At one time the driver allowed me to do that, and I wound up with a lot of scrambled coasters.
Provided you dig about in there and find the file where Patrick shows exactly what command he used to make the ISO with a particular kernel file as bootable with isolinux, it's not terribly complex to generate a new, bootable ISO with a different kernel. (I had to do this for one of those damnable Compaq machines with nothing but the SMART/2P array in it once and I was very glad to have found that little file.)
Once you've downloaded an ISO Image you can mount it as a loopback device. This will give you access to the files in the ISO without you having to burn it to a CDROM first. In order to do this you must have loopback compiled into your Linux Kernel. (Most newer distributions will have this enabled by default). For example if you wanted to mount filename.iso to /mnt/iso you would run the following command: