Mapping a reset vector

2:

• The method of claim 1, wherein utilizing the boot loader to initialize the system includes:
• allocating a Block Exclusion Vector (BEV) to the block device that includes a boot loader;
• and
• loading at least a portion of the boot loader according to the BEV policy.

3:

• The method of claim 1, wherein determining if a block device that includes a boot loader is accessible by the system includes:
• determining if the system supports the remapping of a reset vector;
• and if so,
• detecting if a first boot loader has been swapped with a second boot loader, and
• utilizing a system boot loader policy to remap the reset vector.

6:

• The method of claim 3, wherein
• the first boot loader is included within a fixedly-mounted firmware;
• and
• the second boot loader is included within a removable block device.

9:

• The method of claim 2, further including:
• determining if the Block Exclusion Vector (BEV) allows writing information to the block device;
• and
• if so, allowing data to be written to the block device after an operating system has loaded on the system.

10:

• A system comprising:
• a processor;
• a removable block device including a boot loader;
• and
• a controller;
• wherein the controller is operatively coupled with the processor and the removable block device to facilitate an access qualification mechanism that is capable of facilitating access to specified blocks of the removable block device.

14:

• The system of claim 13, wherein the system is further capable of:
• detecting whether or not the removable block device is communicatively coupled with the processor;
• if so, determining if the access qualification mechanism allows utilizing the boot loader of the removable block device to facilitate initialization of the system;
• if so, utilizing the boot loader to facilitate initialization of the system.

15:

• The system of claim 14, wherein the system is further capable of:
• if the removable device is either not communicatively coupled with the processor or the access qualification mechanism does not allow utilizing the boot loader of the removable block device to facilitate initialization of the system, attempting to find another block device which is both communicatively coupled with the processor and the access qualification mechanism allows utilizing a boot loader of the another block device to facilitate initialization of the system;
• and
• utilizing the boot loader of the another block device to facilitate initialization of the system.

18:

• The system of claim 14, wherein the system is further capable of:
• determining if the Block Exclusion Vector (BEV) allows writing information to the removable block device;
• and
• if so, allowing data to be written to the removable block device after an operating system has loaded on the system.

19:

• An apparatus comprising:
• a controller capable of controlling access to a plurality of block devices, wherein at least one block device includes a boot loader (i.e. a boot loadable block device);
• and
• a Block Exclusion Vector (BEV) logic capable of qualifying access to specified blocks on a block storage device;
• wherein the controller utilizes, at least in part, the BEV logic to control access to the plurality of block devices.

21:

• The apparatus of claim 20, wherein remapping a reset vector includes:
• determining if a system policy allows for boot loader swapping;
• detecting if a boot loader swap from the first boot loadable block device to the second boot loadable block device occurred;
• and
• utilizing the second boot loadable block device to boot a system.

23:

• The apparatus of claim 22, wherein the controller is further capable of:
• determining if the Block Exclusion Vector (BEV) for the second boot loadable block device allows write access to at least a portion of the second boot loadable block device;
• and
• if so, allowing writes to occur to the second boot loadable block device after an operating system has loaded.

26:

• The apparatus of claim 19, wherein the controller is capable of:
• determining whether or not the boot loadable block device is a removable block device;
• and
• if so, utilizing the removable boot loadable block device to boot a system.

27:

• The apparatus of claim 26, wherein the controller is further capable of:
• if the boot loadable block device is not a removable block device;
• determining if a back-up boot loadable block device is available;
• and
• if so, utilizing the back-up boot loadable block device to boot a system.

29:

• An article comprising:
• a machine accessible medium having a plurality of machine accessible instructions, wherein when the instructions are executed, the instructions provide for:
• determining if a bock device controller supports a Block Exclusion Vector (BEV) mechanism;
• if so, determining if a block device that includes a boot loader is accessible by the machine;
• and
• if so, utilizing the boot loader to initialize the machine.

30:

• The article of claim 29, wherein the instructions providing for determining if a block device that includes a boot loader is accessible by the system includes instructions providing for:
• determining if the system supports the remapping of a reset vector;
• and if so,
• detecting if a first boot loader has been swapped with a second boot loader, and
• utilizing a system boot loader policy to remap the reset vector.