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.
hi i'm trying to create a slackware live iso but having trouble.i am following this tutorial http://www.linuxpackages.net/howto.p...e=livecd+HOWTO ...but when i edit isolinux/isolinux.cfg to use the hugesmp.s kernel it keeps looking for bare.i which i can't see..i am trying this with slackware 13.37
The problem is likely due to something else. Are you sure that you are editing the same copy of "isolinux.cfg" actually being used to create the CD? Did you run "mkisofs" again after editing the file?
Look at the ISO image with 7-zip, or look on the CD that you burned. Type out the contents of "isolinux.cfg" on the CD. Make sure that the text in it matches your editing.
When I worked with Isolinux some time ago i had a similar problem. When editing the isolinux.cfg my editor (vim) created a backup copy of that file named isolinux.cfg~ in the same directory. For some reason unknown to me this file was used, not the edited file. After I deleted that file Isolinux worked as intended.
When I worked with Isolinux some time ago i had a similar problem. When editing the isolinux.cfg my editor (vim) created a backup copy of that file named isolinux.cfg~ in the same directory. For some reason unknown to me this file was used, not the edited file. After I deleted that file Isolinux worked as intended.
That may be because Isolinux does not support anything except plain ISO 9660 file names. The "~" character is not allowed in plain ISO 9660 file names. The "mkisofs" program probably truncates the "~" off the end of the backup file when converting file names. That only applies to the few files that Isolinux loads, and not the operating system being booted from CD. I seem to remember having a similar problem when making my own boot CD using GRUB. The "menu.lst~" file was replacing my "menu.lst".
TobiSGD, i deleted the isolinux.cfg~, i also use vim and it seemed to stop looking for bare.i but now it says ... Could not find kernel image: /kernels/hugesmp.s .Yeah Erik_FL i ran mkisofs after. i copied everything from slackware cd1 /kernels to my /livecd/kernels so don't know where it's going wrong.
TobiSGD, i have now give the full path /kernels/hugesmp.s/bzImage but it behaving like an installation cd, like i would normally boot from slackware cd 1 to install
Are you using the initrd.img from the setup CD? It contains the whole setup routine. I just had a look at that Tutorial. You realize that it is more than 10 years old? Also, it states that you need the initrd.img from a Slackware Live-CD.
I doubt that this tutorial will work without that image, otherwise you would have to create your own customized initrd that mounts the CD and switches the root-fs to that CD.
I think this type of creating Live-CDs is gone for years, even a fairly minimal install nowadays wouldn't fit on a CD, so I think that this type of initrd isn't available for newer versions of Slackware. Nowadays Live-CDs use squashfs to compress their filesystem and some type of union filesystem to make changes possible.
I currently also am researching how to create Slackware Live-CDs, but most documentation is outdated and tools either not available anymore or outdated. If I find a solution I will post it back here.
I think it would be easier to use Cooking Up Some Slack (CUSS) for Distribution. LQ Post 'Cooking Up Some Slack (or CUSS) explains how to make your own SlackwareŽ-based distribution.' Additional read if you want to use SlackwareŽ 12.1 or >.
I understand your desire for a LiveCD but you can garner useful information from CUSS.
Plus you can look at LiveCD Salix. Salix is a GNU/Linux distribution based on Slackware. Look at how Salix generates/creates environment or inner working of scripts.
Plus you can look at LiveCD Salix. Salix is a GNU/Linux distribution based on Slackware. Look at how Salix generates/creates environment or inner working of scripts.
Well, I would do that, but the Salix Live scripts are not online anymore or the links in their documentation are outdated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
