#1: boot from USB memory
-------------------------+--------------------------------------------------
Reporter: jjp3 | Owner: parasytic
Type: enhancement | Status: assigned
Priority: major | Milestone:
Component: bootdisk | Version:
Keywords: |
-------------------------+--------------------------------------------------
Changes (by parasytic):
* cc: parasytic (added)
* owner: => parasytic
* status: new => assigned
Comment:
This is a pretty important bug for me, so I'd like to take this. abylons
is exactly right about the BIOS causing problems in some cases. And I
think I have a work-around for it; I built sfdisk from the utils-linux-ng
package, and I want to get rid of the EDD stuff and just trust the kernel
(/sys/block)
On two different Dell machines I have for testing (Vostro 200 and Zino HD)
the BIOS sets the booted drive (especially USB flash drives) to
int13_dev80, and bumps any real hard drives to x81, x82, etc. This is a
problem with the BIOS, but I think it highlights that the BIOS can't be
trusted to determine the "boot device I want to install the OS to".
Thinking out loud for my implementation:
1) Get a list of all hard drives from /sys/block
2a) If there is only one, just use it!
2b) If there is more than one, ask which to use!
3) Get the disk geometry from sfdisk
When asking, it would be a good idea to get as much info about the drives
as possible, like size, vendor strings, etc. I'm not sure how to get the
vendor stuff, even with EDD.
--
Ticket URL: <http://sourceforge.net/apps/trac/unattended/ticket/1#comment:2>
Unattended <https://apps.sourceforge.net/trac/unattended/>
This is a system for fully automating the installation of Windows 2000
Professional and Server, Windows XP, and Windows Server 2003.
------------------------------------------------------------------------------
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
