From owner-freebsd-hackers Mon Oct 16 9:45:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hecky.it.northwestern.edu (hecky.acns.nwu.edu [129.105.16.51]) by hub.freebsd.org (Postfix) with ESMTP id B892837B66D for ; Mon, 16 Oct 2000 09:45:39 -0700 (PDT) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id LAA28973 for ; Mon, 16 Oct 2000 11:45:38 -0500 (CDT) Received: from confusion.net (dhcp089155.res-hall.nwu.edu [199.74.89.155]) by hecky.acns.nwu.edu via smap (V2.0) id xma028219; Mon, 16 Oct 00 11:44:43 -0500 Message-ID: <39EB3051.58E631CA@confusion.net> Date: Mon, 16 Oct 2000 11:44:01 -0500 From: Laurence Berland X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Starting to code Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's a good place to start if you're a university student with limited hardware who wants to jump in and get going with the FreeBSD code. Right now I've got a PPro 200 with 32 MB of ram and lots of disk space (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of tossing Current on also, and maybe making the cvs repo a separate partition so I can share it between current and stable. Mostly at this point I'm looking for a way to jump head first into the code. Where's a good starting point? tia, -- Laurence Berland Intern, Flooz.com Northwestern '04 stuyman@confusion.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message