looking for areas to contribute
Dan Partelly
dan_partelly at rdsor.ro
Wed Mar 23 16:01:01 UTC 2016
For your point 2:
Once the initial kernel build is completed you should rebuild with
make buildkernel KERNFAST=“cfg”
where “cfg” is your config file.
For world :
make buildworld NO_CLEAN=YES.
Relevant manual: build(7)
> On 19 Mar 2016, at 17:52, Littlefield, Tyler <tyler at tysdomain.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
> I've asked this before, but I'm in a better position now to make this
> work.
>
> I'm fluent with C and other languages and want to start contributing
> to BSD. I'm happy to work where ever I can be of use, I love more
> lower level stuff but anything that has me working on code would be
> great. My questions:
>
> 1) How do people usually have their environments set up? I'm thinking
> of running fbsd11 in BHyve where I can do testing, but if there's a
> better way to test that won't require so many resources that would be
> nice as well. I didn't want to break my host with testing since it's
> going to run various other services.
> 2) How do you prevent rebuilding world and kernel for simple patches?
> 3) ideas on what to work on would be great. I haven't gotten into
> really advanced BSD work for a while now, so I haven't found anything
> that is incredibly broken.
>
> Also although this may be off topic, I'm hoping I might find someone
> who uses IOCage here since this seems to be out of the realm of what
> most people do. Has anyone used IOCage on FreeBSD 11? If so, how did
> you manage to fetch the release? I pointed it to the snapshot FTP path
> and it fetched and extracted (freebsd-update failed to get public
> keys), but it doesn't show it as a release. My second thought is if
> I'm working on world then I can just rebuild world under the jail. Is
> this a good solution?
>
> Thanks,
> - --
> Take care,
> Ty
> Twitter: @sorressean
> Web: https://tysdomain.com
> Pubkey: https://tysdomain.com/files/pubkey.asc
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBAgAGBQJW7XXYAAoJEAdP60+BYxejT/YIAIFzhdY6Z0dEWwbqIbXx3sZu
> 5Md/o4rR3Nui5x1DyM7p+g666cmJd+2TX1cl1nkbhYUt9sNiQbrHHfup+pIKGsaU
> F38lkBfGZ+t7vFEgSmiTd9B71IYrLHOkOmgUZE0WMpc3zJs7Y+Stku7kL2R3ej+w
> qaR+bSMpc9RQ6rgtBbKS4ubim5gyjdaOdQpp4FUt40eJGGDN+k+ecc3jgRE6S2z+
> 7F4uwck+NLUhSybH+kjB6HHqX0oRcEu+XqNveFp7kGKY2aFSPdhgPdD+MAoKFunW
> ZzCwCgvY3aaGnKy/VfFP9oQ+P3gdVY4DccnQvufE3AyvNN7d+fl+b4HsZMGXXmI=
> =Ybcf
> -----END PGP SIGNATURE-----
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
More information about the freebsd-hackers
mailing list