SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is a breaking point for all hardware. A facility to use or create a CD will be there for versions up-to 13.37. A new user can be referenced to links that do the job! PV has questioned the continued use of the CD set because things are going to be tight for a new release.
I do agree that the world community does not have the facilities to utilize the net at the broadband speeds we have available.
A bundled set with a USB option would be good option. Even then not all users will have the abilities nor hardware to support fully. At some point PV will make the decision(s).
Click here to see the post LQ members have rated as the most helpful post in this thread.
I agree with the USB key option, but from the 100 or so different machines I have installed Slackware on, or worked on for friends, I can count on one hand the number which have CD without DVD capability. So my input would be:
-DVD with separate disc for 32 and 64
-USB key
-CD (as a legacy media)
Furthermore, I would let the economics of production, and demand (orders) drive the death of CD. As long as people keep ordering them, and they can be made cost effectively, then why drop CDs? But for me, I use DVD and USB keys that I make from the DVD iso.
Depending on how Slackware evolves in the next few releases and the space it will require on a DVD, it might make sense to span it on a DL image rather than multiple single layered DVDs, the only problem with DL media is their price, and burning the image onto said media could be tricky, because a -R DL disc would require L0 (first layer) to be filled up completely, where as +R DL image can have a layerbreak set at any point, plus a DL iso does not have layerbreak info, thus needing an extra file in text format usually, specifying the layerbreak.
Though cool as it may be to have a 32 and 64-bit iteration of Slackware on one entire image, perhaps it is 99.9% doubtful that there would be such an ISO and most likely just be spanned across multiple SL media.
Quote:
Originally Posted by volkerdi
CDs, on the other hand, are rapidly looking like floppy discs to me
One day DVDs will feel that way too, and then Slackware will be jumping onto Bluray, and at that point I wouldn't be surprised seeing 32 and 64-bit Slackware on the same image.
I'd buy this from the slackware store for sure!!! A usb drive with the slackware logo down the side. Bundle it with a T-shirt that promotes the current version and you make my 50 bucks ever time a new release came out ;-)
I'd buy this from the slackware store for sure!!! A usb drive with the slackware logo down the side. Bundle it with a T-shirt that promotes the current version and you make my 50 bucks ever time a new release came out ;-)
Well, we could call the bundle "BFSS": Bundle for Fanatic Sectarians of Slackware.
I would agree dropping the CD format, provided a script is provided on the DVD image to create a bootable CD just like there is to create a USB key.
I do meet machines that only have a working CD that I can use for booting the installation media. The rest of the installation source can come from the NFS/HTTP/whatever.
@rouvas: The README in the isolinux directory already provides you with a command to make an iso. If you plan on getting the packages from NFS/HTTP/whatever then just delete slackware/ from the directory tree before you make the iso. You can also delete anything else you don't need e.g. all the sub-directories except for kernels and isolinux.
For example to make a -current mini install iso. Firstly I would fetch what I need as follows:
Last edited by ruario; 06-28-2012 at 05:39 AM.
Reason: removed -m as it is not relevant to this example; switched my example from wget to lftp as it is easier
@Alien Bob: Damn it, you really have thought of everything! In hindsight I should have checked the mirror-slackware-current.sh options, especially as I ended up spending a little too long thinking about wget's exclude (-X) option and how it works.
Edit: I guess my way might still be useful to those who don't have access to a fast rsync mirror (only ftp or http).
Last edited by ruario; 06-28-2012 at 05:28 AM.
Reason: removed quote to shorten reply
Another thing is to use 'mirror-slackware-current.conf' to exclude;
Quote:
excerpt from 'mirror-slackware-current.conf';
# If you want to exclude more from the DVD ISO than just the ./testing
# directory, you can add the directories to DVD_EXCLUDES.
# The pathnames must be local to the top level and must start with ./
#DVD_EXCLUDES="-x ./testing"
DVD_EXCLUDES="-x ./testing -x ./pasture -x ./source -x ./extra/source"
This is how you can trim the DVD to a convenient size or just get;
Quote:
Slackware-Current Trimmed
The ISO below are <2.3GB + 'ISO images are automatically re-generated within a day if there is an update to the ChangeLog.txt' + These ISOs are created using Alien_Bob's script 'mirror-slackware-current.sh' + Source is not provided on the ISO images below Slackware-current DVD ISO image <- 'x86' for 32bit Slackware64-current DVD ISO image <- 'x86_64' for 64bit
'mirror-slackware-current.sh' along with 'mirror-slackware-current.conf' provide flexibilities for the user to customize the ISO & medium.
I think Pat's main question was what to do for the slackware store. There are a zillion ways to get slackware onto a machine.
I think it's time to go DVD only for the store, then when that isn't enough space then use separate media for x86 and x86_64, or do what slackware 12 did and use dvd1 for the main install and put all of the x/kde stuff on DVD2. Either way works fine for me.
As far as people that need to install on older machines without a CD, just grab the mini cd boot from Eric and do the rest of it from the network or usb stick.
Regardless, what I don't want to see is slackware holding back because of space on optical media. If anything I would like to see some packages in extra that make slackware a little more mainstream such as a pam, iscsi, ldap server, postgres, or other things that are missing from slackware. Not that we all need or want these things (otherwise we would use a different distro) but there has been occasion where I needed features that were not included and ended up building them myself (or using slack builds.org.)
So basically, I don't want a pam linux with some crazy script hack for an init, but I would like to be able to add some features that I need without needing to build everything myself, and while extra does give me some of what I want, it would be great if it can be expanded. I'll even contribute.
One last thing, I would love to see support for postgres added to the standard stuff like php and perl. I don't use mysql anymore because of it's horrible error checking, lacking date support, and other oddities. Slackware is a simple yet industrial strength linux and deserves an option for a database that isn't riddled with quirks and gotchas, like only allowing static values for default data in columns (except for the timestamp hack which is a special static which returns the current time), or lacking sequence support which forces us to use auto_increment which is part of the table and again a hack.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.