В Thu, 29 Nov 2012 17:22:50 -0800 Linda Walsh <suse@tlinx.org> пишет:
You can trace a windows boot -- there is no preload of a memory-resident copy of windows, that then loads windows. The drivers for the hardware are on the disk in /windows/system32/drivers.
On Windows, it reads their boot managager, which then loads 'winload' which *demand*-loads drivers and services from disk -- they aren't all bound in to the kernel in order for it too boot.
To load drivers from \windows\system32\drivers winload needs to include filesystem driver. To be able to read filesystem it must be able to access it first. So either it must include LDM drivers or it must demand that system drive be contained in single partition, even though you converted it to LDM. Functionally intermediate binary that is loaded during boot and includes filesystem and possibly volume manager drivers and logic to load additional drivers on demand is initrd. With the primary difference that initrd supports more than one filesystem, more than one volume manager, places no restrictions on ondisk format, can be used to mount filesystem across networks, can be used to cleanly tear down filesystems during shutdown, ... I definitely forgot something else here. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org