simulating a Hard disk

vanquisher · 08-28-2003, 12:17 AM

Quote:

Originally posted by Dark_Helmet
I would also assume that filesystems are not rquired, because the concept of a filesystem resides in the domain of the OS. A pure simulation of a hard drive does not know, and does not care about a filesystem. All it does it write data to the blocks/sectors it's told to. How that data is interpreted is up to some other entity.

Thanks for this piece Helmet. I totally forgot about that. So, I'm going for a laaaaaarge array then.

Quote:

EDIT
one of which was a task sheduler. You could have a process that was active, sleeping, of blocked, waiting for IO from a device. The project was to implement various scheduling routines (round-robin, static priority, and dynamic priority)

Well, that sounds like my next assignment in my OS course. Totally freaked me out man.

Thanks for the help guys. I think I finally shaped an idea on how to proceed further. Mine may not be the best approach but I'll post my progress in coming days. Thanks a lot.

Robert0380 · 08-28-2003, 01:19 AM

Logging suggestion:

you could have your program make a file when it starts up called hdd.log or something, and instead of holding the information in proram memory, you could write a function to log the info. My C is rusty so i'll use English instead of C.

Code:

int log(char* data)
{
     open the file
     append to it
     close it
     reutrn some value to indicate success or fail (always do error checking)
}

if you are REAALLY lazy..

int read_log() 
{
    system("echo \"disk read accord..yadda yadda\" >> hdd.log ");
}

int write_log()
{
   system("like the above");
}

that way u let the OS handle the opening and closing (and appending).

vanquisher · 08-28-2003, 01:28 AM

Quote:

Originally posted by Robert0380
Logging suggestion:

you could have your program make a file when it starts up called hdd.log or something, and instead of holding the information in proram memory, you could write a function to log the info.

That's what I'm doing. Logging every transaction would be nice. Thanks for the suggestion.

kev82 · 08-28-2003, 04:13 AM

i wish i did comp sci so i could do an operating systems course, or a computer vision course, but i guess i'll just stick to my math. as for the logging just pass the disk an ostream& or as you seem to prefer C a FILE* so that the disk doesnt have to worry about opening/closing files, also a verbosity setting adds a nice touch.