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.
I happen to have external drive case with USB interface. The drive inside classic SATA hard drive partitioned with DOS/MBR scheme. Drive has some data which can't be deleted at the moment and one free primary partition. That would be /dev/sdb3. I was thinking to mark sdb3 as active, copy data from ISO image with dd and create bootable installation image. Could it actually work that way ?
Do you want to copy an installation disk over to the drive so you can take the drive to various computers to install it, or do you want to install Slackware to that partition so you can use that drive as your normal OS?
I'd like to copy installation disk over one of the primary partitions on external drive. In order to install on other computers, yes. It does not necessarily need to be Slackware installation only, could be other OS's, too. Actually, this is not a Slackware specific question, or even Linux specific, but the answer would be interesting to many out there.
If you have an MBR system, installing Grub2 to the MBR of that drive pointing to the partition you want to use. You could then put any number of iso bootable files there and boot them. You would need to install Grub2 first and manually create your grub.cfg file.
You would first format with a Linux filesystem sdb3, then create the directory sdb3 with a boot directory in it and mount the partition. You would lose any data on sdb3 currently. There are numerous sites explaining booting an iso directly but if you have a specific distribution in mind, post back and someone might be able to give you an example.
Of course, if you already have a bootable Linux with Grub2 on that drive, the only step necessary is creating the menuentries in grub.cfg.
Simply copying an iso image to a partition with dd or some other means is not going to make it bootable. You need a bootloader and Grub2 works fine for this.
Not sure why you would want to mark the partition as 'active' unless you plan to put some windows software on it. It won't be a problem but I've never found it necessary with any Linux. I'm not sure Grub2 will directly boot a windows iso, at least I'm unaware of any method but you can extract the iso contents of windows and copy to a partition and boot with a correct menuentry.
What am I trying to do is use sdb3 as bootable CD or stick. External disk has partition table and 4 partitions, 3 primaries and one extended. It also has MBR code in first sector. My reasoning is that any BIOS capable of booting from USB and booting from DOS/MBR partitions should be able to boot any OS installation image on active partition. In theory.
At the moment I have LILO on the external disk with Slackware on /dev/sdb2 and some Windows on /dev/sdb1. LILO is installed in /dev/sdb2 and it used to boot both Slackware and Windows.
Booting LILO on /dev/sdb2 and other OS on /dev/sdb3 sounds fine. But if that works, then marking /dev/sdb3 as active partition and booting from it seems even simpler. Besides, I am not sure how to setup LILO to boot from ISO image.
However, you gave me an idea. If I could boot Slack on /dev/sdb2 then I could probably boot iso image on sdb3, as well. If the latter is made active. And I can try it out right away, without waiting for several gigs to be copied over USB. Thanks, you have helped me a lot.
I have never played with USB boot so far. I am able to boot in LILO on old /dev/sdb drive. LILO is installed on /dev/sdb2 which is marked as 'active'.
However, I tried to copy FreeDOS ISO to /dev/sdb3 with dd. Then I made sdb3 active. Machine won't boot ISO image, the message is "Error: missing operating system". dd command line was:
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,484
Rep:
If I remember right, lilo will only boot one OS, so unless you changed which partition it is trying to boot from, it is still trying to boot sda2. Maybe you should use grub, or syslinux/extlinux, as your boot manager.
If I remember right, lilo will only boot one OS, so unless you changed which partition it is trying to boot from, it is still trying to boot sda2. Maybe you should use grub, or syslinux/extlinux, as your boot manager.
lilo can boot as many OSes as you can add to the lilo.conf (although, I suppose there could be a limit, but I've had at least 10 entries listed before and haven't had problems booting any of them). It supports both booting the OS directly using entries for its kernel and root device or chainloading to another bootloader.
I got it working. What I did is format free disk partition with file system appropriate for OS which needs to be installed. Then copy all the files from installation ISO image to free partition. After that I set the LILO which I had installed already on the disk to chain boot it ("other" section). Installation files can be copied by mounting ISO with "-o loop" switch.
It is probably easier with GRUB2, which can boot ISO directly. And with recent UEFI BIOS which might also be able to that. However, I need to try that yet. Hope this could help someone out there.
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,484
Rep:
Quote:
Originally Posted by bassmadrigal
lilo can boot as many OSes as you can add to the lilo.conf (although, I suppose there could be a limit, but I've had at least 10 entries listed before and haven't had problems booting any of them). It supports both booting the OS directly using entries for its kernel and root device or chainloading to another bootloader.
Yes, you are right, I am wrong, I had forgotten, (in my defence, it has been many years since I have used lilo), sorry for that, OP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.