Kernel build fail for generic on r256122 (if_cxgbe)
Details on pastebin: http://pastebin.com/raw.php?i=dNzL3yXR ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Light humour
ah my miss interpretation sorry :) On 03/05/2013, Eitan Adler wrote: > On 3 May 2013 08:31, Paul Webster wrote: >> it was not really meant to be trolling I am sorry if you see it that >> way; I just thought it was as my original posts state quite funny, >> never thought it would would raise so many follow up posts though :) > > antibsd is the troll, not you. > > > > -- > Eitan Adler > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Light humour
it was not really meant to be trolling I am sorry if you see it that way; I just thought it was as my original posts state quite funny, never thought it would would raise so many follow up posts though :) On 02/05/2013, Eitan Adler wrote: > On 2 May 2013 08:21, David Demelier wrote: >> 2013/4/28 Paul Webster : >>> Just got this link on IRC, (freenode/##freebsd) was so funny I thought >>> I would see if I could get any of you guys to spit out you're coffee >>> :) >>> >>> http://antibsd.wordpress.com/ >> >> Do not post any comment on that website ! The user will replace any >> content you write by something like "You're article is excellent, >> pointing exactly the facts". >> >> All of the comments are probably edited by the maintainer >> > https://gs1.wac.edgecastcdn.net/8019B6/data.tumblr.com/tumblr_lmpcbtar6f1qafrh6.jpg > > -- > Eitan Adler > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Light humour
Just got this link on IRC, (freenode/##freebsd) was so funny I thought I would see if I could get any of you guys to spit out you're coffee :) http://antibsd.wordpress.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: looking for help from ppp users
Hey there gary, this works for talktalk/UK ADSL modem in PPPoE mode, or did beore my house move ill double cobnfirm in 6 days when my new line is active. #talktalk: set reconnect 999 1 set device PPPoE:xl0 # replace xl1 with your Ethernet device set authname my-house-phone-num...@talktalk.net set authkey myAdsl password set dial set login add default HISADDR set speed sync set mru 1492 set mtu 1492 set ctsrts off enable echo set echoperiod 15 enable lqr set lqrperiod 15 enable ipcp disable ipv6cp disable dns set server /tmp/pppoe-adsl0 .. 0177 add! default HISADDR add! default HISADDR6 On Sat, 15 Dec 2012 06:14:10 -, Eitan Adler wrote: On 3 December 2012 10:41, Gary Palmer wrote: While not commenting on the correctness of the current contents, the userland PPP section of the FAQ appears to mostly deal with dialup modems. I suspect more people use it now to do PPPoA or PPPoE for some form of DSL link and there probably needs to be some effort to address the differences. I've never used PPP in any sense. Any chance I could enlist you to help write some content? I could turn it into docbook, edit it, etc. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Request for merge into 9.x
Hello I was recently reading about your work on the Ralink 2860, I run an EEEPC 1000 at the moment and have always wanted to run freebsd on it; however due to the wireless not being supported and a hatred for hanging usb dongles handing everywhere; I had to run linux. I am no driver developer, but I would love to give your driver a trial run on 9.1-RELEASE or -STABLE if easier, I am quite sure once everyone with an eeepc realizes we finally have a working wifi card; they will be most impressed :) as an aside, if you could leave me some simplish instructions on howto actually generate the kernel module in 9.0/9.1 -RELEASE I would happily report how well it works -- paul ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD to use the NEW pf syntax.
I only really need one question answered in honesty; I personally think that by forking our own version of PF we have essentially made something totally different to what everyone wants to use. Which is fine, but because of that development of new features have dropped behind. If we had kept up with OpenBSD's version even if we trailed it by one MAJOR release; at least part of the development would have been done. So now we end up in a situation where we have these firewalls, IPFW2,ipf,pf(modded) and users wanting the newer features of OpenBSD's pf. So timewise the fork of pf may have actually cost more in time rather than less. I don't however think the 'solution' to the problem is just to say no to the userbase by not even trying to port across the newer pf. I think we should look at bringing it across, slowly and seeing what the uptake is like; in a few MAJOR releases we can start to look at which of the firewalls realistically are not used that much and should be deprecated. On Wed, 21 Nov 2012 15:20:19 -, Ermal Luçi wrote: On Wed, Nov 21, 2012 at 3:52 PM, Gleb Smirnoff wrote: On Wed, Nov 21, 2012 at 03:44:13PM +0100, Ermal Lu?i wrote: E> Cherry-picking would be when tehre is reasonable similarities. E> Also another argument to do this would be simplicity on locking as well as E> i told you when you started the changes. You were wrong. OpenBSD doesn't move towards SMP model. Locking more recent pf is not simplier, but the opposite. I am sorry but you are asking arguments i already have given you. You didn;t listen once and i do not expect this time as well. E> Though i am open to work together on this to merge the new syntax thorugh a E> whole bulk merge rather than cherry-pick. How many bugs have you closed after the previous bulk import? Why should we expect anything good from new import if the previous one was a PITA? Well you have used it for your work so it was not so PITA. Most of the ones you closed had message 'This is to old to be true'; 'I have re-written PF and this should be fixed'. And still I don't see any answer on the question: what exact features or perfomance improvements are we going to obtain from "the new pf"? See above. E> You already have 'broken' some functionality as if-bound in FreeBSD 10.x so Is there any PR filed on that? I didn't even receive a mail about that. I really do not think you do the right approach or the right communication on this. Sorry for replying to you ;). -- Totus tuus, Glebius. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf)
Forward notice: I sent this to freebsd-pf originally and did not CC -current, but as the issue would affect current and the more opinions the better... I have sent it here too. -- Cheers, daemon -- original message Good day all, I am aware this is a much discussed subject since the upgrade of PF, I believe the final decision was that to many users are used to the old style pf and an upgrade to the new syntax would cause to much confusion. There was a recent debate on ##freebsd about this issue and I was inclined to mail in and get your opinions; basically it boiled down to the majority of users wanting either: 1) To move to the newer pf and just add to releases notes what had happened, and 2) my own personal opinion: creating 'pf2-*' as a kernel option tree, basically using the newer pf syntax and allowing users to choose. I would be interested to know the feedback from you guys as to be honest there seems to be quite a few users who actually DO want the new style format and functionality that comes with. I Attached the log of the conversation just for reference. -- Thank you for your time -- Paul G Webster 'daemon' Using Opera's revolutionary email client: http://www.opera.com/mail/* daemonik (~ad...@mail.originate.com) has joined ##freebsd Is the implementation of PF on FreeBSD up to date yet? no * stormcrow (~phyde...@c-24-126-183-121.hsd1.ga.comcast.net) has left ##freebsd and it won't ever be, we (retardedly) forked it with some random guy's patches rather than updating it it's rare that that question asked about *any* part of the base OS will be answered with "yes" doh. booo @ random patches blakkheim that was truly a stupid move i agree any chance of getting them to 'take it back' they think freebsd users are too stupid to adapt to the newer pf syntax and "thousands will upgrade without knowing and be left with an unreachable system" or some bs like that is there anything that pf can do that ipfw cannot do check the freebsd-pf mailing list illuminated (or feel free to post and complain) blakkheim: That's pretty damn . . wow might be worth a few emails to all the lists asking for other users to post into the pf list to support moving to the correct pf maybe we can implement the newer pf as 'pf2' FreeBSD presently doesn't have ALTQ support included in the generic kernel, correct? Is there an alternative to ALTQ? daemon: i think so too daemon: Is it really that hard to shout in the appropriate places to properly inform users? What about release notes? Anybody who doesn't read release notes deserves what's coming to them. that's what i said! * chrisb has learned to read MOVED and UPDATING closely Huh . . that kind of behavior is why no one respects anyone/thing associated with GNOME anymore . . daemonik, I dont see it being that hard to use both the 'ramdon guys patches' version of pf as the default for a few releases putting the newer version of pf as 'pf2' therefor satisfying both channels of thought there certainly should be A WAY of using the newer version posting these thoughts to freebsd-pf@ is much more likely to invoke a change (or at least a poll or something) than on irc daemon: No . . the noobs are the ones who should have to use a pf-something. I bother to read the release notes, I want to use the correct version of the software. Why should I have to suffer? Why should I change when they're the ones who suck? * nightwalk has quit (Ping timeout: 276 seconds) I'll make a post later tonight. I hope that others see these messages and also articulate their thoughts on the mailing list. FreeBSD should hold a high standard for something as important as PF. daemonik, if you did read release notes you would see 'ad the new version of pf is pf2' there is no need to upset users without cause; as the 'patched' pf is the default for the tag 'pf' at the moment making the new version 'pf2' is literally much more sane and certainly a huge degree less antagonistic How do I find the size of a folder? And for that matter how do I search a man page? du -sh dirname and use /string to search Thanks blakkheim I would rather read the release notes seeing that the WRONG version of PF gets deprecated to pf-legacy as it ought to be knowing that those who don't read the release notes will have a bad day. Referring to the CORRECT and latest stable version of PF as "PF2" would make FreeBSD . . well, look about as incompetent as certain Linux distros sometimes do to say the least. daemonik, transistion time should always be taken into account on any system; if we did was I was suggesting then 'pf' would be the new version in -CURRENT but for later 9.x releases it would still have to be as I pointed out above i recall a number of features having 2 tagged to the name UFS2 for one or was it FFS2 and i think IPFW2 its quite a common practice; sudeenly changing a major feature/system is just generally what makes people cry especially when i
