You are not logged in.
Howdy all,
In trying to learn more about the way distro's, and live images are put together, I am messing around with the bl-Helium_amd64+build.iso.
I am wanting to unpack, add/remove files and repack for use.
So far, I have mounted the iso using:
sudo mount -o loop bl-Helium_amd64+build2.iso /mnt/iso
And then because this is read only, I copy the results to a separate folder "BunsenLabs"
in my home directory.
I then make changes.
Here is where I am getting stuck.
So far, I have tried re-creating the iso using:
genisoimage -o cd.iso -R -J BunsenLabs
Which creates the iso. I tried burning and reboot here, but no go. (figured).
All of the guides I found showed using mkisofs to do this, but I guess xorriso is the new program.
So, I then tried using this for xorriso to create a hybrid image hoping this would work:
xorriso -as mkisofs \
-o output.iso \
-isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin \
-c isolinux/boot.cat \
-b isolinux/isolinux.bin \
-no-emul-boot -boot-load-size 4 -boot-info-table \
CD_root
Unfortunately, I'm not sure of the propper usage here either.
I also tried using a usb stick with dd, but am also unsure of the format. I have always used cd's, and simply never had one that held over a couple of g's until now.
I wiped the usb completely, made the filesystem, made a new partition using the whole device (ext4), then dd to the usb:
sudo dd if=cd.iso of=/dev/sdb1 bs=4M
Trying to boot with the usb just gives me a blinking prompt.
So, I am not stuck on any one method, just sharing part of what I have already tried that seems to be in the right direction.
Certainly open to other ways to do this, and while I prefer learning terminal commands, if a gui is available that works, I'm open to that as well until I can get this figured:)
Last edited by sleekmason (2018-07-10 16:45:21)
Offline
Are you following this guide https://wiki.debian.org/DebianInstaller/Modify/CD ?
Offline
Are you following this guide https://wiki.debian.org/DebianInstaller/Modify/CD ?
Wild. In all my searching, the above link didn't come up. Must not have been asking the right questions.
I will check it out. Thank you!
Offline
On quick glance, this should be...
sudo dd if=cd.iso of=/dev/sdb bs=4M;sync
sdb with no number after it, and sync to make sure the image isn't still writing after the terminal prompt returns. Or using cp...
sudo cp cd.iso /dev/sdb;sync
https://forums.bunsenlabs.org/viewtopic … 784#p70784
I don't know anything about repacking the ISO, I'm afraid.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Are you following this guide https://wiki.debian.org/DebianInstaller/Modify/CD ?
Wild. In all my searching, the above link didn't come up.
has happened to me too, esp. with debian's wiki.
something wrong with the whole debian.org site in that respect. it's labyrinthine. unsearchable.
Offline
On quick glance, this should be...
sudo dd if=cd.iso of=/dev/sdb bs=4M;sync
Yep! That works real well. Thank you:)
So far, using the instructions from the wiki, I have successfully extracted the ISO image, made a change, remade the ISO, put it onto a USB stick, and have the initial screen come up. It's a win in my book. At least a bit of one.
I was hoping to replace the vmlinuz image's and the initrd.img in "live" with an updated kernel and have it boot into a different kernel, but nope! that didn't cut it. Suggestions? Maybe a file or two that needs a simple line update?
Anyway, exploring around in there is pretty neat. I will keep working at it to be sure.
has happened to me too, esp. with debian's wiki.
something wrong with the whole debian.org site in that respect. it's labyrinthine. unsearchable.
Makes me feel a little better:) I wonder why it's like that? Well, glad it's there anyway. The mess I was creating before seeing the link was getting out of hand.
Offline
You'd need to rebuild the initrd and update-grub, I am pretty sure. Grub needs to know the kernel name and any changes to the kernel and need a rebuilt initrd. You might need to do all that from a chroot environment, I think.
Offline
You'd need to rebuild the initrd and update-grub, I am pretty sure. Grub needs to know the kernel name and any changes to the kernel and need a rebuilt initrd. You might need to do all that from a chroot environment, I think.
Okay, so this is cool. You are saying the system needs to be live mounted/chroot in order to make that kind of change? It literally needs to update grub:)
So, yeah, if it isn't just grabbing files as needed, but IS the environment, that changes things considerably. Is this the case?
If so, debootstrap?, or something better? This means that when finished making changes, I can simply exit the environment with changes intact? And, do I have to get files into the chroot environment first? I guess they could be grabbed through any path, so maybe not necessary.
Offline