4MLinuxThis forum is for the discussion of 4MLinux.
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 don't think #16 is relevant, because the OP uses other distros.
@#13 (MichaelK): I trust your huge experience/expertise, but I don't quite understand. Could you provide additional tutoring here? I did find this article: https://superuser.com/questions/6832...so-is-a-hybrid
This may have actually happened to me because I vaguely remember (rare) things mysteriously not booting in the past.
Edit added several days later: thanks for #19!!! I did some more web searching and found this, which seems to be a great tutorial: https://www.rodsbooks.com/gdisk/hybrid.html
My favorite Hands-on Booting (one of the few books I own because I depend on my local public sclibrary.org) unfortunately makes no mention of even USB flash drive booting, only CD / DVD ( though it has a brief appendix on live isos which I think is a totally different issue)
file 4MLinux-40.0-64bit.iso
4MLinux-40.0-64bit.iso: ISO 9660 CD-ROM filesystem data 'CDROM' (bootable)
file hybrid.iso
hybrid.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'CDROM' (bootable)
I believe you but usually a hybrid ISO will have a DOS/MBR boot sector, a non-hybrid does not and a non-hybrid ISO should not be able to boot from USB.
thanks,
now it works with the hybrid iso but I saw that while using jwm it uses 1.8 gb of ram in live, sparkylinux 300/400 mb, crunchbang ++ also and mabox as well.
!!!,
A CD/DVD boots using a completely different process from a regular hard drive which is why copying the ISO file using the dd command fails. An ISO file by convention is an ISO 9660 filesystem, the standard defines how data is written to the disk and how to make it bootable. One of the first methods to convert an ISO file to boot from USB was syslinux. The file was extracted to an existing USB drive formatted with a FAT32 filesystem and then syslinux was the boot loader. isohybrid adds a MBR to the ISO file when created which allows it to "natively" boot from a USB drive. Most distributions these days provide a hybrid ISO file which is why most people might expect using the dd command to just work. When booted the filesystem still appears like a read only CD/DVD despite it being on a flash drive.
thanks,
now it works with the hybrid iso but I saw that while using jwm it uses 1.8 gb of ram in live, sparkylinux 300/400 mb, crunchbang ++ also and mabox as well.
You can also choose "Legacy Installer" from the hybrid.iso menu. This will make it possible for you to start the installation process even if you have only 128 MB of RAM.
You can also choose "Legacy Installer" from the hybrid.iso menu. This will make it possible for you to start the installation process even if you have only 128 MB of RAM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
