Is it possible to chainload into a Linux system in a fully loaded Windows Desktop?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Is it possible to chainload into a Linux system in a fully loaded Windows Desktop?
Hello intelligent Linuxers,
Out of curiosity, can you chainload a Linux system via a Windows executable within Windows at the ordinary desktop?
Knowing windows there would be enough holes to write at any memory address without "permission", but can it be done with a humble executable? Or is Windows just too active, without the chance of nothing happening at any one point so that everything can be exited cleanly non-existent?
I'm not asking for a program or guide to do this and neither do I aim to do it. As I've stated it is all out of curiosity on whether or not some sort of protection is in place to stop this kind of thing.
If I wanted to hijack a Windows system I'd just use a firewire port anyway...
For older Windows (95,98,Me) there was loadlin that would do this. http://en.wikipedia.org/wiki/Loadlin
Another approach is that used by Cygwin. http://cygwin.com/ It is very useful to me for the ability to ssh (with X11 forwarding) to a Linux box and also for access to *nix text tools such as awk, grep and sed.
For older Windows (95,98,Me) there was loadlin that would do this. http://en.wikipedia.org/wiki/Loadlin
Another approach is that used by Cygwin. http://cygwin.com/ It is very useful to me for the ability to ssh (with X11 forwarding) to a Linux box and also for access to *nix text tools such as awk, grep and sed.
Wow, thankyou. Loadlin was exactly what I was posting about. It is a shame it is no-longer usable now with the NT era.
Cygwin + bash = winash
Thanks Allend.
Quote:
Originally Posted by saikee
It would be called a virtual machine.
Chainloading and VMs have nothing in common, unless you use grub in your vm. Chainloading is where the current program/os replaces itself with another in the same memory area. VMs just nest OS's within each other, in different memory areas but with the second running in an emulated environment so it (mostly) thinks it is the main and only OS.
I think Loadlin works in real mode as a Dos program operating in a command prompt. If it has a desktop version then I never ran into it. The Windows has to be shut down in order to boot up the kernel which has to be made available in the Loadlin directory or at those days conatined inside a floppy. Loadlin is exactly waht its name implies to "Load Linux". It might has its place before LIlo and Grub were fully developed.
The Grub4Dos system is possibly a newer equivalent.
Chainloading is a term used by one boot loader to boot another boot loader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.