> Surely people can move on from the low hanging fruit of a port that needs
> a ./configure & make install, to minor code or makefile changes, to specific
> new functionality to from the scratch coding.
Not to sound like a dick, but this illustrates some of what I'm saying:
If I hold up o
From: "Bret S. Lambert"
Or, in short, we need to not deter people straight away, and accept that
perhaps sometimes decent programmers start from ones that make lots
of mistakes.
Perhaps a ports TODO similar to the NetBSD ports TODO might help; it
doesn't require quite the same level of kernel o
> Or, in short, we need to not deter people straight away, and accept that
> perhaps sometimes decent programmers start from ones that make lots
> of mistakes.
>
> Perhaps a ports TODO similar to the NetBSD ports TODO might help; it
> doesn't require quite the same level of kernel or userspace hac
On Mon, Apr 19, 2010 at 04:15:02PM +, Thordur Bjornsson wrote:
> > And if you value your sanity, stay out of anything resembling filesystems.
> This is a lie.
>
> Hacking on filesystems, and the VFS layer in general is a very rewarding
> experince, just ask Bob.
>
> NFS for example, has been
On Mon, 19 Apr 2010 16:57:38 +0200 "Bret S. Lambert"
wrote:
> src/sys/
> kern/ <- generic stuffs (signals, scheduling, vnodes,
> syscalls) net/<- generic net stuffs (interface handling, pf,
> routing) netinet{,6}/ <- IPv{4,6} stuffs
> net*/ <- non-IP network stuffs
>
On Mon, Apr 19, 2010 at 8:48 AM, Adam M. Dutko wrote:
> 1) Are there areas that are easier for "relative newbies" to start in
versus
> other areas? I know this depends on a lot of things, to include
experience.
> Hypothetically, someone that has some C experience, but not a lot of
kernel
> (and
> And if you value your sanity, stay out of anything resembling filesystems.
This is a lie.
Hacking on filesystems, and the VFS layer in general is a very rewarding
experince, just ask Bob.
NFS for example, has been a source of joy for OpenBSD developers for
years!
>> 2) Is there something like
On Mon, Apr 19, 2010 at 11:48:02AM -0400, Adam M. Dutko wrote:
> On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> >
> > ... ...
>
>
> > Hopefully this is useful for somebody.
> >
>
> It is, thank you.
>
> With regard to the other questions I peppered everyone with... :-)
>
> 1)
On Monday, April 19, "Adam M. Dutko" wrote:
>
> 1) Are there areas that are easier for "relative newbies" to start in versus
> other areas? I know this depends on a lot of things, to include experience.
> Hypothetically, someone that has some C experience, but not a lot of kernel
> (and subsyste
On Mon, Apr 19, 2010 at 11:48:02AM -0400, Adam M. Dutko wrote:
> On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> >
> > ... ...
>
>
> > Hopefully this is useful for somebody.
> >
>
> It is, thank you.
>
> With regard to the other questions I peppered everyone with... :-)
>
> 1)
On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> ... ...
> Hopefully this is useful for somebody.
>
It is, thank you.
With regard to the other questions I peppered everyone with... :-)
1) Are there areas that are easier for "relative newbies" to start in versus
other areas? I k
On Mon, Apr 19, 2010 at 09:59:06AM -0400, Adam M. Dutko wrote:
> The obvious answer to this questions is "Just read the source..." but I
> still want to ask if someone is aware of a good overview of the OpenBSD
> source code? I've watched several presentations by Ted Unangst, Jason Dixon
> and co.
The obvious answer to this questions is "Just read the source..." but I
still want to ask if someone is aware of a good overview of the OpenBSD
source code? I've watched several presentations by Ted Unangst, Jason Dixon
and co. and there seems to be a good amount of information spread across the
w
13 matches
Mail list logo
