The grammar makes that book fairly painful to read :-|
Hi, I would love to hear your feedback. It is the style or the correctness? I am really appreciate if you can show me the few incorrect usages of the grammar.
Operating Systems: From 0 to 1
31–40 of 82 posts
Re: Operating Systems: From 0 to 1
#32Earlier quoted context omitted.
> Author here. Yes, it's a x86 operating system. However, rather than getting around A20, it focused on protected mode instead. You still have to open the A20 gate in the bootloader if you want to access a memory adress that has bit 20 (counting from 0) be set to 1 (you probably want) - even if you switch to protected mode. The only exception is if you boot from UEFI instead of BIOS - in this case the A20 gate is alr…
In the Volume 3, it is said that: "In protected mode, the IA-32 architecture provides a normal physical address space of 4 GBytes (2 32 bytes). This is the address space that the processor can address on its address bus. This address space is flat (unsegmented), with addresses ranging continuously from 0 to FFFFFFFFH. This physical address space can be mapped to read- write memory, read-only memory, and memory mapped…
The A20 gate would affect both real and protected mode, so to be truely compliant, you should be opening it even for a protected mode OS. It was originally a purely hardware hack forcing an address line(A20, or the 21st address line) to stay low, thus "wrapping" addresses from 1mb-2mb to 0-1mb, so it would have affected real or protected mode identically. On modern hardware, there is a chance that A20 is (against the accepted spec) default open, or possible not implemented.
Re: Operating Systems: From 0 to 1
#33The hallmark of a Good book is that it should leave you wanting more. That's what the book is all about.
Have you read the book?
Re: Operating Systems: From 0 to 1
#34Re: Operating Systems: From 0 to 1
#35Earlier quoted context omitted.
This is what I'm planning to read as soon as I've learned assembly: http://www.brokenthorn.com/Resources/OSDevIndex.html
I graduated from that guide :) You can see the repo here, written entirely in NASM: https://github.com/tuhdo/os-study The problem is that the guide is out of date in terms of toolchain, and you need to figure out many things by yourself, especially if you want to develop on Linux. My book helps you to understand how to learn and write x86 with Intel manuals (this is really important!), understand how to craft a custo…
Oh, good to know! I'll keep that in mind and keep a bookmark of your book and your implementation.
Actually, I wanted to start writing an OS by following the BrokenThorn tutorial and was quite naive. After reading some pages it came to me that I don't know much assembly and so I started learning from Jeff Duntemanns Assembly book [1]. As far as I can see, your book also teaches the basics of assembly, it seems more friendly to beginners. Maybe it will be a better start for me. Thanks for putting in the hard work!
Re: Operating Systems: From 0 to 1
#36Earlier quoted context omitted.
Hi, I would love to hear your feedback. It is the style or the correctness? I am really appreciate if you can show me the few incorrect usages of the grammar.
I can tell you're not native. Have the book proofread by someone.
Yes, I'm not native. For that reason I tried to use simple grammar and sentences, and did go through paragraph by paragraph through a grammar checker until the end of chapter 4. I will try to improve it gradually.
Re: Operating Systems: From 0 to 1
#37Earlier quoted context omitted.
I can tell you're not native. Have the book proofread by someone.
Yes, I'm not native. For that reason I tried to use simple grammar and sentences, and did go through paragraph by paragraph through a grammar checker until the end of chapter 4. I will try to improve it gradually.
It is better to proof read for correctness. I myself want to point out few grammatical stuffs and looking for the source in Github. You can simple create a repo or add the source text to the current repo, so that people can easily fix these issues for you by giving pull requests.
You don't want people judging this excellent book based on few language quirks here and there.
Re: Operating Systems: From 0 to 1
#38Earlier quoted context omitted.
Yes, I'm not native. For that reason I tried to use simple grammar and sentences, and did go through paragraph by paragraph through a grammar checker until the end of chapter 4. I will try to improve it gradually.
It is better to proof read for correctness. I myself want to point out few grammatical stuffs and looking for the source in Github. You can simple create a repo or add the source text to the current repo, so that people can easily fix these issues for you by giving pull requests. You don't want people judging this excellent book based on few language quirks here and there.
Thanks. I will upload the source soon. As it is written in Lyx, not sure everyone will find it comfortable though. You can always open an issue in the meantime though.
Re: Operating Systems: From 0 to 1
#39Earlier quoted context omitted.
I can tell you're not native. Have the book proofread by someone.
Yes, I'm not native. For that reason I tried to use simple grammar and sentences, and did go through paragraph by paragraph through a grammar checker until the end of chapter 4. I will try to improve it gradually.
Regular spellchecker can correct mistyped words, but not, for example, words miused in a particular context, missing the/a, etc. Try some of those more advanced contextual spellcheckers and proofreaders like Grammarly or LanguageTool.
Re: Operating Systems: From 0 to 1
#40Well this has got to be one of the more ambitious things I've seen on HN. I wonder if the guy behind SkyOS is still doing operating systems. http://www.skyos.org/