From mboxrd@z Thu Jan 1 00:00:00 1970 From: ron minnich To: 9fans@cse.psu.edu Subject: Re: [9fans] getting sdC0/nvram right in /bootdir In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Date: Sun, 9 Nov 2003 08:37:07 -0700 Topicbox-Message-UUID: 837f616c-eacc-11e9-9e20-41e7f4b1d025 On Sat, 8 Nov 2003, Russ Cox wrote: > Where else would it look? Yep, and I can easily take that code, as you just did, and now we've got two chunks of code to think about anytime anything changes; precisely why I did not want to do that. I don't like it. Two is one too many. That's the problem we've got right now with 9load/plan9. Just to get 9load at all to work on some of my nodes I had to grab stuff out of plan 9 and put it back into 9load. It was a real pain. That's code bloat -- duplicating capability in lots of different places when it should only be in one place. Growing a ram disk with stuff like fdisk/prep is not code bloat. It's ram disk bloat, maybe, but not code bloat. I just can't get excited about 560KB kernels vs 2 MB kernels when my CF parts are so cheap. The time difference to read it in is, realistically, 0. bootdir size is the wrong metric. Thanks for the fixed up part.c, it's neat, and I'll probably just use it and ignore my own arguments I just made :-) thanks ron p.s. All opinions my own, and doubtless wrong :-)