Browsing this Thread:
1 Anonymous Users
|
Re: Volume Manager
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
So each DeviceID would be a type of device? How about something more generic, as why not have it be possible to boot on USB or whatnot... if ObtainDeviceID is to work like some kind of "database of registered devices" then I suggest something like, "type"(storage, pointer, ...), "removable"(yes or no) and so on. Also, returning the same name for the same device(regardless of what's been added or removed since its registration) I would think is important.
Posted on: 2004/4/1 20:05
|
|||
|
||||
|
Re: Volume Manager
|
||||
|---|---|---|---|---|
|
Home away from home
|
I was thinking of something to provide functions similar to the following
ObtainDeviceID( char * BaseID ) RegisterController( struct StorageController Controller) RemoveController( struct StorageController Controller) RegisterDrive( struct StorageDrive Drive) RemoveDrive( struct StorageDrive Drive) ObtainDeviceID would be called with i.e BaseID = "CD" and would return a unique (unused) proper name to use "CD1","CD2" depending on whats allready registered. The other functions would register the devices/controllers in a semaphore protected linked list, providing the info we need in a nice and quick manner (i.e dont have to check every ".device" in the system and query them if they are even the type we want).
Posted on: 2004/4/1 15:09
|
|||
|
||||
|
Volume Manager
|
||||
|---|---|---|---|---|
|
Home away from home
|
As you might know ive taken the task of updateing the "AROS Install Process" onboard.
Most things are done and commited, but the issue remains of partitioning the drives and prepareing the bootloader (with detection and support for multiple OS's) Now my big problem is that under Amiga, AROS and and current flavour, there is no way to query what controllers are available and what physical drives (unpartitioned etc) exist. After discussion with a few folk i think the solution is a volume manager (or perhaps to extend the current partition.library) That would a> Require defineing the volume manager and its functions b> Coding the volume manager c> Change existing AROS drivers to register with the new volume manager and register all the drives they have found on theyre "bus". but the end result is we then have an easier method of finding (suitable) drives and checking if they can actually be a boot drive etc. Thoughts??
Posted on: 2004/4/1 14:40
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
