Brendan's Guide to OS Testing

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
User avatar
Combuster
Member
Member
Posts: 9301
Joined: Wed Oct 18, 2006 3:45 am
Libera.chat IRC: [com]buster
Location: On the balcony, where I can actually keep 1½m distance
Contact:
Contact Combuster

Re: Brendan's Guide to OS Testing

Post by Combuster »

Could you put it into the wiki (you wrote it, it's your intellectual property)?
Why not link it yourself, next time :wink:
"Certainly avoid yourself. He is a newbie and might not realize it. You'll hate his code deeply a few years down the road." - Sortie
[ My OS ] [ VDisk/SFS ]
Top
embryo

Re: Brendan's Guide to OS Testing

Post by embryo »

Combuster wrote:
Could you put it into the wiki (you wrote it, it's your intellectual property)?
Why not link it yourself, next time :wink:
The link is for one person, but wiki is for all.
Top
embryo

Re: Brendan's Guide to OS Testing

Post by embryo »

And one point I have found while reading the Brendan's guide - it can really help if developers would run their OS on the machines of each other. But some protocol is required to do this. It can be like this - when OS reaches state with USB driver implemented it can be provided as a USB-stick image with a USB-logging capabilities. So any friendly developer just writes the image on some USB media and runs it on the machines he has, then OS writes logs on the USB and resulting file in the end can be sent to the OS author. It seems not very complex.

One more point - Brendan can make a business of OS testing charging 5-10 dollars per run on all he's computers :)
Top
Post Reply

Return to “OS Development”