From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom To: 9fans@cse.psu.edu, Russ Cox References: <5e753da568cf6fa8232c0efcbfb4429c@swtch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <5e753da568cf6fa8232c0efcbfb4429c@swtch.com> Subject: [9fans] kernels Message-Id: <20060310172513.DEA6D2173CA@dexter-peak.quanstro.net> Date: Fri, 10 Mar 2006 11:25:13 -0600 Cc: Topicbox-Message-UUID: 12200b84-ead1-11e9-9d60-3106f5b1d025 i consider the fact that you can cut down your configuration to a minimum and get a kernel with a limp rather than nothing a big bonus. if anybody can give me some pointers on where to start looking, i'd like to see why my machine is failing on mp startup. - erik "Russ Cox" writes | What causes differences between the three situations usually *isn't* the | kernel but rather the kernel configuration or plan9.ini. For example, | the installer kernel doesn't include devusb, devlpt, or devaudio, all | to keep it a little smaller. We've seen problems where people install | successfully and then something about the usb scan during the regular boot | makes their system not boot. There's very little one could do about that | besides put usb into the installer kernel so that it breaks earlier. | But we can't, for space reasons. As another example, the plan9.ini | during the install sets *nomp=1 but the regular plan9.ini does not. | So if you something about the SMP code doesn't like your system, as we | saw a few days ago, then the installed system won't boot. These are all | bugs to be fixed, but forcing us to debug them on the boot floppy instead | of after install time doesn't really seem like the right solution to me.