Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
I would like to create a bootable CD based on Slackware's bootable floppy images. Basically, I don't want to use floppies and I don't wanna have to download a full bootable ISO just to use as a boot CD later. I would like to create a bootable ISO small enough to fit on mini-cdr or mini-cdrw that would allow to start the installation process. Then I can mount the full ISO images or just use a premounted directory option. Could I just combine bare.i and rootdisks images into an ISO? Is this even possible? If no one has tried this, I could possibly be creating a tool that not only I can use but others as well.
All you really need is the kernel and the initrd from ISO1. See directions inside the isolinux folder for making a custom CD. You just need the isolinux folder. You can then have isnatllation files on HD or other CD.
The initrd contains the same setup routines found on the floppies. You can also use install.zip, which is like zipslack, in that it runs from a FAT and also contains the same setup routines.
Ok, im confused now. I downloaded only the files I want in the iso file. I placed them all in under one folder, changed dir to that folder and ran mkisofs. This is what I end up with:
mkisofs -o /iso/slackware.iso -R -J -V "Slackware 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 Install CD" .
Warning: creating filesystem that does not conform to ISO-9660.
mkisofs 2.0.3 (i686-pc-linux-gnu)
Using RAWRI000.EXE for ./isolinux/sbootmgr/RAWRITE13.EXE (RAWRITE12.EXE)
Using RAWRI000.EXE for ./bootdisks/RAWRITE13.EXE (RAWRITE12.EXE)
Using RAWRI000.EXE for ./rootdisks/RAWRITE13.EXE (RAWRITE12.EXE)
mkisofs: No such file or directory. Unable to open disc image file
Any suggestions as to what's going on? Thanks.
Do you have a root folder named : "iso"?
mkisofs -o /iso/slackware.iso
^ You are sending the .iso to a folder named: /iso
Sounds like that may be the prob. Probably better to just send it to your home dir anyway.. something like:
just make sure the dir exists and has proper permissions.
BTW if you use the command the way Patrick V. has it as an example on the Disk, it would send it to the /tmp directory-folder.
This obviously isn't necessary, but just a thought.
Oh BTW if you use the proper 'extensions' while making your disk you can avoid having it re-name files like rawrite above... (It is making them stick to the 8+3 Standard for ISO's...) You can override this, forget the command... just look it up in the man.
Last edited by bonecrusher; 08-11-2004 at 09:13 AM.
Yes, I made sure those dirs were created prior to running the command. It gave me the same message with /tmp/slackware.iso in there. So I figure I create a different dir. I'll look up the renaming option cause that was going to be my next concern. I wouldn't be surprised if the renaming is causing the error message. I'll keep you posted.
the option is -l "Allow full 32 character filenames. Normally the ISO9660 filename will be in an 8.3 format which is compatible with MS-DOS, even though the ISO9660 standard allows filenames of up to 32 characters. If you use this option, the disc may be difficult to use on a MS-DOS system, but this comes in handy on some other systems (such as the Amiga). Use with caution."
The only thing I can think of is that your permissions are bad. Come to think of it '-J' should be fine for Joliet extensions (In addition to a ISO9660 table)... So I dunno... check permissions and let me know.. if that's not it, get back to me. I take it that you are root when doing this?
As a note:
Although it appears you are doing this, I make mine by first ALWAYS cp'ing the CD I wanna 'copy' off from the CD to it's own directory on the harddrive, and then after it is in it's own dir, I delete or add what I want.. (I never do the graft-points thing as it just starts getting confused after awhile...) And thats about it.. make sure your permissions are set right for the DIR where the CD is being read, and for where the file (ISO) will be written to. And make sure your 'root', and that's about it...
But like I said, if it's not permissions, then let me know, and I iwll try and help you fig it out.
Last edited by bonecrusher; 08-11-2004 at 04:15 PM.