Why is it impossible to hybridise 4mlinux?
by freemedia2018 from LinuxQuestions.org on (#4T305)
I realise this is not an issue with 4mlinux alone, but it is not an issue that I have found in many distros either. I'm hoping the maintainer can explain it.
Typically I use isohybrid (when someone else hasn't already) and the dd command to create bootable media. This results in an error (invalid boot catalogue) and no effort to search out why this happens or when it should be expected is very clear on the matter.
Instead of using a simple and generic command like dd, the solution seems to be to use a 3rd-party tool like unetbootin. My question is: why is that even necessary? Since this seems to be happening to a handful of distros at least, please don't think I'm trying to be critical of 4mlinux. But this is something I'd like to understand for both curiosity and project development.
Typically I use isohybrid (when someone else hasn't already) and the dd command to create bootable media. This results in an error (invalid boot catalogue) and no effort to search out why this happens or when it should be expected is very clear on the matter.
Instead of using a simple and generic command like dd, the solution seems to be to use a 3rd-party tool like unetbootin. My question is: why is that even necessary? Since this seems to be happening to a handful of distros at least, please don't think I'm trying to be critical of 4mlinux. But this is something I'd like to understand for both curiosity and project development.