Contribution to FreeBSD network stack
Hi All, I am interested to contribute to FreeBSD network stack. I found some projects at http://wiki.freebsd.org/Networking . But could not figure out how to start working on the same. Please help. Thanks, Shashi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Contribution to FreeBSD network stack
On Sun, 31 Jan 2010, shashidhara none wrote: I am interested to contribute to FreeBSD network stack. I found some projects at http://wiki.freebsd.org/Networking . But could not figure out how to start working on the same. Please help. Hi Shashi-- The FreeBSD network stack is a very large piece of code, and there are lots of opportunities to get involved helping to measure and improve its behavior, add new features, etc. Could you say a bit more about your background -- have you done much kernel programming and/or network stack programming before? Robert ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Contribution to FreeBSD network stack
On 1/31/10 3:50 PM, shashidhara none wrote: Hi All, I am interested to contribute to FreeBSD network stack. I found some projects at http://wiki.freebsd.org/Networking . But could not figure out how to start working on the same. Please help. Which project have you chosen? Do you have relevant education and/or previous experience? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Spin down HDD after disk sync or before power off
imo this patch takes good care of the problem. would be nice to have it in HEAD. cheers. alex Warren Block schrieb am 2010-01-30: > On Fri, 29 Jan 2010, Jung-uk Kim wrote: > >On Friday 29 January 2010 05:38 pm, Warren Block wrote: > >I am not 100% sure but I think it should be something like the > >attached patch. > Yes, I had the two commands backwards. So let me try to summarize: > ad_shutdown uses ATA_FLUSHCACHE writes out any cached data, but does > not park the heads. At powerdown, the heads do an emergency park, > which is louder than a normal park and possibly damaging. > Adding ATA_STANDBY_IMMEDIATE after the ATA_FLUSHCACHE will park the > heads more quietly and possibly more safely. Should do no harm, at > least. > ad_spindown looks like it's meant to spin the disk down for sleep > operations, and does some higher-level things. > I suspect flushcache and standby should be as close together as > possible to avoid the chance of anything getting back into the cache > or spinning the disk back up. > Anyway, testing this use of ad_spindown inside ad_shutdown brought > back the GLINK on shutdown. > A fixed version of the earlier patch that does flushcache and then > standbyimmediate is attached. > -Warren Block * Rapid City, South Dakota USA ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] extending/completing brandelf's OS knowledge
so it seems some people consider the patch a useful extension to brandelf and other would like brandelf to keep it's core functionality. also some people would like brandelf to move from base to ports. alex Alexander Leidinger schrieb am 2010-01-25: > Quoting Kostik Belousov (from Mon, 25 Jan 2010 > 11:16:25 +0200): > >On Mon, Jan 25, 2010 at 10:01:29AM +0100, Alexander Leidinger wrote: > >>If it was to brandelf a static linux executable so that the FreeBSD > >>system does not reboot when executing the static linux executable, > >>then I would say it does not need to be reported and we still need > >>brandelf in the base system. > >>If someone says that exactly this case has been fixed recently: it > >>would be great to hear on emulation@ about cases where brandelf is > >>still needed. > >If static linux binary contains .note.ABI-tag section, and I believe > >that relatively modern binaries do, then brand is autodetected. > Our linuxulator is not restricted to modern binaries. I remember > reports from people which run or try to run binaries (proprietary > stuff, all limitations of non-open-source software applies) from > linux 2.2 or even older. It's been a while since I've seen such a > report, but as it typically just works, I can not tell that we can > be sure that nobody wants to run binaries which do not fit your > definition of "relatively modern". > Bye, > Alexander. > -- > "No, don't protest. I'm telling you their thoughts, not mine." > -- Vito Corleone, "Chapter 2", page 74 > http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = > B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = > 72077137 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Weekend PR smashing
On Fri, 22 Jan 2010, Giorgos Keramidas wrote: > On Sun, 17 Jan 2010 13:30:50 -0800, "R. Tyler Ballance" > wrote: > > Are there similar resources I've not stumbled across yet? I would like to > > help, > > I have but one machine running -CURRENT and sporadic free time over the > > weekends. > > Hi there. I just noticed this post in among others in -hackers. If you > don't know about the bugbuster team already, you should check it out. > There's a mailing list at freebsd-bugbusters and an IRC channel at the > EFnet network. Righteo, I stumbled across that shortly after my email to the list, I've been lurking in there since (rtyler). > > Since you are looking for pointers to get you started, the following may > help a bit: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/ > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ > > Finally, it's worth noting that it is not a huge problem if you only have > weekend-time to contribute. We welcome all the help we can get, so please > feel free to jump in and help in any way you can with the existing bugs (or > new ones that you have noticed). I certainly get that impression, one of the things that concerns me is the sheer number of PRs with patches that either have been committed without the PRs being updated, or the patches are simply sitting idly in PRs. The list by the bugbusters waiting for committers to check them out is pretty huge as well: http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html It's a little difficult to muster up too much motivation to fix issues when the fixes will then sit waiting for committer review for months on end. Without annoying committers, is there any way I can help get patches "through" and into the tree in less than a lunar cycle? ;) Cheers, -R. Tyler Ballance -- Jabber: rty...@jabber.org GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero Blog: http://unethicalblogger.com pgpAXeZvmgpyz.pgp Description: PGP signature
