From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <775b8d190601190243i12161bafkeed0752dbf6f8f8a@mail.gmail.com> Date: Thu, 19 Jan 2006 21:43:31 +1100 From: Bruce Ellis To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] GNU binutils: you can't make this shit up In-Reply-To: <7f6f168f5d8ed3ddd20ffc2bd069d95e@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060119082946.19064.qmail@web32707.mail.mud.yahoo.com> <7f6f168f5d8ed3ddd20ffc2bd069d95e@terzarima.net> Topicbox-Message-UUID: dfdc088a-ead0-11e9-9d60-3106f5b1d025 can i put this in m book? --- forsyth the way to get good portability is to have clear, well-designed interfaces that abstract away from hardware peculiarities, and map those to the hardware (rather than, say, reflecting in the interfaces the union of every peculiarity of all hardware known to you at the time). some of the hard bits about kernel development are: - getting accurate documentation for the processor, devices, existing bootstrap, etc. - getting anything loaded into the wretched machine at all - deciding how your kernel should look, what it should do, how it should ch= ange - working out a good infrastructure for networks, devices coming and going, power, etc. - finding time and/or money to do any of it