Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'll try to give you a few tips/hints - a clear answer isn't that simple:</p> <ol> <li><p>An ext2 filesystem written in C is just C. C is just a programming language - you can use C++, plain assembly or a few others (A few os'dever use D) - but not a "managed" language etc. But it is important that you have a rock solid understanding of this language. In my opinion assembly is a MUST (Take a look at the scheduler in an operating system -> plain assembly)</p></li> <li><p>Do you really want to write an USB driver ? It isn't "just" a simple USB driver (Layer of abstractions). Why a USB driver and not a floppy disk or CD driver (Believe me - a floppy driver in 32 bit protected mode isn't that hard) ?</p></li> <li><p>Please focus on your project. Of course Linux (Early versions) and Minix have example code, but take care of the design structure (Monolithic/Microkernel or hybrid-kernel) - and don't mix it, write your own code. </p></li> </ol> <p>Please make on step after the other. You wrote a basic IRQ handling and the plan is to write a keyboard/mouse driver - write the keyboard driver ! Don't dream about loading and executing files (Rom wasn't built in one day).</p> <p>You have to read documentations, for example the Intel manuals or other "books". A very popular forum is osdev.org - take a look at the wiki. As twalberg said, it's a very huge module - stay focused on the main parts of your operating system.</p> <p>I know, this is not the answer to your question - but it's important not to go in the wrong direction and dream of a fancy UI or something like this ;)</p> <p><a href="http://f.osdev.org/" rel="nofollow">osdev.org forum</a> <br> <a href="http://www.osdev.org/" rel="nofollow">osdev.org wiki</a> <br> <a href="http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html" rel="nofollow">Intel manuals</a> <br></p> <p>And a few other books in my book shelf can you find here (Tanenbaum, Silberschatz with Peter Galvin - great books!): <br></p> <p><a href="http://wiki.osdev.org/Books" rel="nofollow">Books</a></p>
    singulars
    1. This table or related slice is empty.
    1. POCustom Kernel: Implement filesystem
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USswaechter
    1. USswaechter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCustom Kernel: Implement filesystem
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your reply! For 2: USB came up to my mind out of the blue. I was also considering emulating a floppy on a USB and writing the appropriate driver for it I don't dream of implementing a UI of any sort but I would like to get some sort of a filesystem working on it. Or do you suggest taking up a slightly less daunting task such as process communication?
      singulars
      1. PO
      1. USplaknas
    2. COI wrote a floppy driver, but after looking back I would take "El torito". You can emulate a floppy disk or use it as a normal CD with GRUB: http://wiki.osdev.org/Bootable_El-Torito_CD_with_GRUB_Legacy With GRUB and a multiboot header you can load modules - take a look at it (maybe to load some parts)
      singulars
      1. PO
      1. USswaechter
    3. COPlease tell me if I am on the right track here. Currently, I boot my kernel binary off a pendrive with the help of Grub. If I want to come anywhere close to implementing a filesystem, my first step will be to handle the syscalls such as open et al., before I can even go about detecting it? On the other hand, if I can manage a custom implementation, I can get a ramshackle of a filesystem?
      singulars
      1. PO
      1. USplaknas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload