<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="0.92">
<channel>
	<title>Dryice Liu's Blog</title>
	<link>http://dryice.name/blog</link>
	<description></description>
	<lastBuildDate>Tue, 31 Aug 2010 12:01:11 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>install Minix CD-ROM-2.0 on qemu</title>
		<description>While when I doing the "2008 plan" I found there's something I didn't finished last year. Among them is learning the Minix code. I've read all the principle chapters, and left reading the source code behind and never finished that. So to make a good start for this year, I ...</description>
		<link>http://dryice.name/blog/minix/install-minix-cd-rom-20-on-qemu/</link>
			</item>
	<item>
		<title>Why MULTICS is so slow</title>
		<description>Well, everyone in the *nix world heard about the MULTICS system, and because it's so slow, Unix was developed.

And today, when I reading the memory management chapter of Minix, I understand part of the reason why MULTICS is so slow: To locate a single address in the memory, it will ...</description>
		<link>http://dryice.name/blog/minix/why-multics-is-so-slow/</link>
			</item>
	<item>
		<title>different i-node for different file type?</title>
		<description>This is mostly a note for myself.

In 3.2.4, it is said that "for a special file, this i-node contains the major device number, and the minor device number". This is different from what we know for normal files, where the i-node contains file access time, etc.

It is not effecient to ...</description>
		<link>http://dryice.name/blog/minix/different-i-node-for-different-file-type/</link>
			</item>
	<item>
		<title>disk IO: interleave</title>
		<description>I was reading about disk IO this morning. In chapter 3.1.3, it is said that the disk need to be formatted with the number interlaving, so that we'll need less disk circlings to get the data we need.

My question is, all these is based on one assumption: that the buffer ...</description>
		<link>http://dryice.name/blog/minix/disk-io-interleave/</link>
			</item>
	<item>
		<title>chapter 1</title>
		<description>I've finished reading Chapter 1 today. This chapter talks on the bird view. Most concept are pretty familiar with me. There are two things stroke me:

	The Minix core only have 59 system calls to be POSIX compitable. I never thought it could be so less...
	Why the best is the best. ...</description>
		<link>http://dryice.name/blog/minix/chapter-1/</link>
			</item>
	<item>
		<title>the start</title>
		<description>I've started a new plan to learn about operating system internals.

I've got a pretty high score for the operating system class when I was in school, however, that's only the theory. I read the first edition of the Minix book when I was in school, but didn't finish that before ...</description>
		<link>http://dryice.name/blog/minix/the-start/</link>
			</item>
	<item>
		<title>Damm Small Linux</title>
		<description>I gave Damm Small Linux a try today. I've heard it before but this article makes me decided to try it out.

There are many ways to boot DSL, CD, USB, or from a host OS, as I'm still concerning the many old PCs that can't boot from USB, I decided ...</description>
		<link>http://dryice.name/blog/usb_key/damm-small-linux/</link>
			</item>
	<item>
		<title>bochs virtual network</title>
		<description>device type fbsd: guest OS can't communicat with host OS. There must be another physical box available. And this made accessing the internet from the guest OS quite complicated in my situation.

device type tun: several google searches didn't show a successful story. I remember I saw a tun device for ...</description>
		<link>http://dryice.name/blog/freebsd/bochs-virtual-network/</link>
			</item>
</channel>
</rss>

