This is a discussion on Creating a custom slackware distribution within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi, I am interested in creating a custom slacke=ware disk.What I planned to do is creating a slackware disk ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I am interested in creating a custom slacke=ware disk.What I planned to do is creating a slackware disk with packages what i need? for example I don't want network packages to be in first disc so I replace it with kde and creating a boot custom disc I need. Is it possible in Slackware linux? Please help me and give me some links to do this. Thanks in advance |
| |||
| Raghul wrote: > Hi, > > I am interested in creating a custom slacke=ware disk.What I > Try http://cookingupsomeslack.com/ -- it looks to have at least a starting point for what you want to do. |
| ||||
| Raghul wrote: > Hi, > > I am interested in creating a custom slacke=ware disk.What I > planned to do is creating a slackware disk with packages what i need? > for example I don't want network packages to be in first disc so I > replace it with kde and creating a boot custom disc I need. Is it > possible in Slackware linux? Please help me and give me some links to > do this. Hi, I just did exactly that: leave out GNOME and a few apps, keep only KDE as window manager, and then cram everything onto one CD. Here's how you go about that. 1) Create a directory LFS (as in "Linux From Slack"). 2) Copy the contents of Install CD 1 into that directory. 3) If you want to use KDE for example, copy the contents of the slackware/kde/ directory into LFS/slackware/ Now we're going to strip down the whole thing. 1) Every package consists of three files: .tgz, .tgz.asc and .txt. You can delete all three for every package you want to get rid of. 2) Every package group contains a file called 'tagfile'. Edit this accordingly, and use 'SKP' for every deleted package. So your installer won't attempt to install nonexistent packages. 3) Similarly, edit 'maketag' and 'maketag.ez' in every package group, and simply delete the lines referring to deleted packages. 4) If you delete whole package groups - say, GNOME - you can modify your install script accordingly. Edit LFS/isolinux/setpkg, and simply delete the lines referring to nonexistent package groups. 5) Now check the size of your LFS/ directory tree. If it's no more than 700 MB - or whatever fits on your CD, you can go ahead and make the iso. To do that (according to isolinux/README.txt) get into the top level Slackware directory (The one with ChangeLog.txt in it) and issue a command like this to build the ISO image in /tmp: mkisofs -o /tmp/slackware.iso -R -J -V "Slackware Light Install" \ -hide-rr-moved -v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \ -sort isolinux/iso.sort -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot -A "Slackware Light Install CD" . Ah, yes: you can safely ignore whatever error message mkisofs gives you about the result not being an iso file system blah blah woof woof. Now you can safely burn the iso with whatever you use for that (cdrecord, k3b, ...). One last thing: since this isn't Slackware anymore, edit isolinux/message.txt and change the name of your distribution. "Welcome to Slightware Linux", for example. Or "Welcome to some light distribution based on Slackware Linux 10.1". As Alan Hicks pointed out, this is a legal issue... the more so since there will be 30,000 copies made from my "custom" CD, to go with a magazine. Enjoy! Niki Kovacs |