From owner-freebsd-hackers Thu Jan 13 13:45:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id C77DB14C29 for ; Thu, 13 Jan 2000 13:45:07 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id QAA48936; Thu, 13 Jan 2000 16:44:59 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001132144.QAA48936@blackhelicopters.org> Subject: Re: Reading the kernel sources In-Reply-To: <387E38F7.2DC0C433@softweyr.com> from Wes Peters at "Jan 13, 2000 1:43:35 pm" To: wes@softweyr.com (Wes Peters) Date: Thu, 13 Jan 2000 16:44:59 -0500 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > Michael Lucas wrote: > > > > I find myself in a contract where I sit for eight hours a day and wait > > for something to break. It pays obscenely well, so I'm putting up > > with the tedium. > > > > So, if I was to sit down and start reading /usr/src/sys, where's the > > logical place to start? Or should I start elsehwere? Or is there no > > logical statring place, and I should just assimilate it all en masse? > > Start with the PR database. Grab a PR, see if you can figure out what makes > it go wrong, and then see if you can make it go right. Call this "directed > research" of anyone asks what you're doing. Gut reaction: "Geez, I'd like to learn how to swim." "No problem! Just tie these cinderblocks to your wrists and ankles, jump off the deep end, and you'll be ready to go." Second reaction: Ah, what the hell. I might actually fix something. ==ml > Remember, real hackers run -CURRENT on their laptops. ;^) PS: Anyone know the status of zp0 in -current? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message