Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, May 12, 2019, 9:28 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > Eugene Grosbein wrote: > > > 11.05.2019 22:59, Julian H. Stacey wrote: > > > > > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > > > >> > > > I've posted a review to remove obsolete 10 and 10/100 Ethernet > drivers > > > as previous approved in FCP-101. > > > The following drivers are slated for > > > removal from FreeBSD-HEAD (to be FreeBSD-13): > > > > > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, > xe > > > >>> > > > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > >>> spare) that will never be able to upgrade. > > > >> > > > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > > >> What kind of hardware do they have (CPU and memory-wise)? > > > > > > > > Thanks for question. I ran a quick check: > > > > cd /usr/src; > > > > # Apply my patches: > > > > # customise `pwd` > > > > # http://www.berklix.com/~jhs/bin/.csh/customise > > > > cd /sys/amd64/conf > > > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > > > DUAL.small:device ed > > > > FILM.small:device ed > > > > KING.small:device ed > > > > LAPA.small:device ed > > > > LAPD.small:device ed > > > > LAPL.small:device ed > > > > LAPN.small:device ed > > > > LOFT.small:device ed > > > > MINI.small:device ed > > > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz > 0x1 > > > > SLIM.small:device ed > > > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > > > WIND.small:device ed > > > > > > I've asked not for configuration files but for description of hardware. > > > ed(4) supports many different models. Some of them do 10Mbps only > > > but some are 100M-capable including PCI-connected. > > > > > > And it's interesting to know what is CPU and memory type/amount of > boxes. > > > > Info I had long pre saved, exported here: > > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ > > Many boxes run newer releases than logs show, but eg dmesg shows memory > etc. > > It would help if you could run this from the hosts directory above and > post the output here, I doubt anyone besides me well bother looking > any further than this email at this data, but they well if you post > this output: > > find . -type f | grep /dmesg | xargs egrep 'CPU:|real memory|Ethernet' > > That should give us machine name by file path, CPU type, memory and > what ethernet cards are in it. > > I found one box, the second one I looked at, > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/logs/blak/dmesg0 > that clearly has enough CPU and memory to run 13: > CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) > real memory = 536858624 (511 MB) > ed0: at port 0x240-0x25f iomem 0xcc000-0xc > irq 5 pnpid EDI0119 on isa0 > ed0: [ITHREAD] > ed0: WARNING: using obsoleted if_watchdog interface > ed0: Ethernet address: 00:00:b4:36:a5:04 > > > Re Gary's: > > > 2) what versions of FBSD is Julian now running on his hardware? > > > 3) does he ever plan to upgrade this hardware to >= FBSD 13? > > > > Not many, if any of them; I should idealy find time to purge some, > > but I also have sundry newer PCs, & spare ed etc cards, so a pity to > loose ed. > > > > > > More generaly It won't be just me with ed. With 13 I can power up any > time, > > (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more > globaly. > > > > But sys admins often don't have time to read developer lists like > > current@ & arch@. So developer considering zapping things, will > > not be seen by users it will hit later. > > > > First many will know is seeing in a RELNOTES "XYZ will be removed > > in release [0-9].[0-9]" No chance to answer an earlier "Are many > > still using XYZ, we're thinking of deleting it ?" > > I believe all of the proposed cards have been announcing > they are gone in FreeBSD 13 starting at FreeBSD 12. > > I am NOT clear if these gonein notices got backported to > 11, if not they should be ASAP as getting notice out to > the 11.3 users is important too. > > > If ed is the biggest legacy NIC, best be cautious ? > > I agree to some extent, but have no hard use evedence. > Last time I ran the reports from nycbug dmesg reports. Ed was rare starting in 7, and absent 9 and newer. That suggests it's once dominant position has decayed to almost nothing in the 25 years since it was king. I'd included this data at some point in the past, I thought. Warner > (BTW I also have 2 boxes running today's current, not just old Rels here.) > > > > Cheers, > > Julian > > -- > > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich > Aachen Kent > > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in > EU. > > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers > died. > > ___ > > freebsd-current@freebsd.org mailing list > >
Re: FCP-101: obsolete driver removal planned for 2019-05-18
> Eugene Grosbein wrote: > > 11.05.2019 22:59, Julian H. Stacey wrote: > > > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > > >> > > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > > as previous approved in FCP-101. > > The following drivers are slated for > > removal from FreeBSD-HEAD (to be FreeBSD-13): > > > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > >>> > > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > >>> spare) that will never be able to upgrade. > > >> > > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > >> What kind of hardware do they have (CPU and memory-wise)? > > > > > > Thanks for question. I ran a quick check: > > > cd /usr/src; > > > # Apply my patches: > > > # customise `pwd` > > > # http://www.berklix.com/~jhs/bin/.csh/customise > > > cd /sys/amd64/conf > > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > > DUAL.small:device ed > > > FILM.small:device ed > > > KING.small:device ed > > > LAPA.small:device ed > > > LAPD.small:device ed > > > LAPL.small:device ed > > > LAPN.small:device ed > > > LOFT.small:device ed > > > MINI.small:device ed > > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz > > > 0x1 > > > SLIM.small:device ed > > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > > WIND.small:device ed > > > > I've asked not for configuration files but for description of hardware. > > ed(4) supports many different models. Some of them do 10Mbps only > > but some are 100M-capable including PCI-connected. > > > > And it's interesting to know what is CPU and memory type/amount of boxes. > > Info I had long pre saved, exported here: > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ > Many boxes run newer releases than logs show, but eg dmesg shows memory etc. It would help if you could run this from the hosts directory above and post the output here, I doubt anyone besides me well bother looking any further than this email at this data, but they well if you post this output: find . -type f | grep /dmesg | xargs egrep 'CPU:|real memory|Ethernet' That should give us machine name by file path, CPU type, memory and what ethernet cards are in it. I found one box, the second one I looked at, http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/logs/blak/dmesg0 that clearly has enough CPU and memory to run 13: CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) real memory = 536858624 (511 MB) ed0: at port 0x240-0x25f iomem 0xcc000-0xc irq 5 pnpid EDI0119 on isa0 ed0: [ITHREAD] ed0: WARNING: using obsoleted if_watchdog interface ed0: Ethernet address: 00:00:b4:36:a5:04 > Re Gary's: > > 2) what versions of FBSD is Julian now running on his hardware? > > 3) does he ever plan to upgrade this hardware to >= FBSD 13? > > Not many, if any of them; I should idealy find time to purge some, > but I also have sundry newer PCs, & spare ed etc cards, so a pity to loose ed. > > > More generaly It won't be just me with ed. With 13 I can power up any time, > (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more > globaly. > > But sys admins often don't have time to read developer lists like > current@ & arch@. So developer considering zapping things, will > not be seen by users it will hit later. > > First many will know is seeing in a RELNOTES "XYZ will be removed > in release [0-9].[0-9]" No chance to answer an earlier "Are many > still using XYZ, we're thinking of deleting it ?" I believe all of the proposed cards have been announcing they are gone in FreeBSD 13 starting at FreeBSD 12. I am NOT clear if these gonein notices got backported to 11, if not they should be ASAP as getting notice out to the 11.3 users is important too. > If ed is the biggest legacy NIC, best be cautious ? I agree to some extent, but have no hard use evedence. > (BTW I also have 2 boxes running today's current, not just old Rels here.) > > Cheers, > Julian > -- > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Rod Grimes rgri...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
Eugene Grosbein wrote: > 11.05.2019 22:59, Julian H. Stacey wrote: > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > >> > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > as previous approved in FCP-101. > The following drivers are slated for > removal from FreeBSD-HEAD (to be FreeBSD-13): > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > >>> > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > >>> spare) that will never be able to upgrade. > >> > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > >> What kind of hardware do they have (CPU and memory-wise)? > > > > Thanks for question. I ran a quick check: > > cd /usr/src; > > # Apply my patches: > > # customise `pwd` > > # http://www.berklix.com/~jhs/bin/.csh/customise > > cd /sys/amd64/conf > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > DUAL.small:device ed > > FILM.small:device ed > > KING.small:device ed > > LAPA.small:device ed > > LAPD.small:device ed > > LAPL.small:device ed > > LAPN.small:device ed > > LOFT.small:device ed > > MINI.small:device ed > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz 0x1 > > SLIM.small:device ed > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > WIND.small:device ed > > I've asked not for configuration files but for description of hardware. > ed(4) supports many different models. Some of them do 10Mbps only > but some are 100M-capable including PCI-connected. > > And it's interesting to know what is CPU and memory type/amount of boxes. Info I had long pre saved, exported here: http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ Many boxes run newer releases than logs show, but eg dmesg shows memory etc. Re Gary's: > 2) what versions of FBSD is Julian now running on his hardware? > 3) does he ever plan to upgrade this hardware to >= FBSD 13? Not many, if any of them; I should idealy find time to purge some, but I also have sundry newer PCs, & spare ed etc cards, so a pity to loose ed. More generaly It won't be just me with ed. With 13 I can power up any time, (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more globaly. But sys admins often don't have time to read developer lists like current@ & arch@. So developer considering zapping things, will not be seen by users it will hit later. First many will know is seeing in a RELNOTES "XYZ will be removed in release [0-9].[0-9]" No chance to answer an earlier "Are many still using XYZ, we're thinking of deleting it ?" If ed is the biggest legacy NIC, best be cautious ? (BTW I also have 2 boxes running today's current, not just old Rels here.) Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, 2019-05-12 at 10:45 -0700, Rodney W. Grimes wrote: > > 12.05.2019 8:21, Warner Losh wrote: > > > > > >> I've posted a review to remove obsolete 10 and 10/100 > > > Ethernet drivers > > > >> as previous approved in FCP-101. > > > >> The following drivers are slated for > > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, > > > vx, wb, xe > > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show > > > box of > > > > spare) that will never be able to upgrade. > > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > > What kind of hardware do they have (CPU and memory-wise)? > > > > > > There are no 100M ed variants. There are some PC Card variants > > > that have 100M MII connections, but they are limited to about > > > 12Mbps due to bus limits. Even the PCI ones didn't have 100M mii > > > connections. > > > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 > > adapter. > > Not sure if ed(4) supports RTL8029AS. > > That is what I was hunting for, but I can not seem to > locate a data sheet on that. > > I also thought there was a 100mb version of the DP83905, > but can not seem to locate any data thier either. > > Given this lack of findable data I shall continue to support > the ed removal, unless Julian comes up with the needed criteria, > and with holding my own fact that I do have a pile of these > around, but they are not in use and are only retained for > testing and resurection of ancient things. > We should not lose track of the fact that the operative question here isn't "are you using an ed(4) device?", but rather "do you have systems containing an ed(4) device which are capable of running freebsd 13 and that you plan on updating to freebsd 13 or later?" Many of the systems that contained these old devices don't have enough ram to run a modern version of freebsd. If you can't update the system to 13, you don't need ongoing ed(4) support. And make no mistake, ongoing support IS the issue -- it costs manpower we don't have much of to maintain old device drivers. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
> 12.05.2019 8:21, Warner Losh wrote: > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet > > drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > > There are no 100M ed variants. There are some PC Card variants that have > > 100M MII connections, but they are limited to about 12Mbps due to bus > > limits. Even the PCI ones didn't have 100M mii connections. > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. > Not sure if ed(4) supports RTL8029AS. That is what I was hunting for, but I can not seem to locate a data sheet on that. I also thought there was a 100mb version of the DP83905, but can not seem to locate any data thier either. Given this lack of findable data I shall continue to support the ed removal, unless Julian comes up with the needed criteria, and with holding my own fact that I do have a pile of these around, but they are not in use and are only retained for testing and resurection of ancient things. -- Rod Grimes rgri...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
12.05.2019 8:21, Warner Losh wrote: > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > >> as previous approved in FCP-101. > >> The following drivers are slated for > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > spare) that will never be able to upgrade. > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > What kind of hardware do they have (CPU and memory-wise)? > > There are no 100M ed variants. There are some PC Card variants that have 100M > MII connections, but they are limited to about 12Mbps due to bus limits. Even > the PCI ones didn't have 100M mii connections. There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. Not sure if ed(4) supports RTL8029AS. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
On Friday, 10 May 2019, FreeBSD Core Team Secretary < core-secret...@freebsd.org> wrote: > The FreeBSD Core Team is aware of recent controversial statements made > on social media by a FreeBSD developer. We, along with the Code of > Conduct review committee, are investigating the matter and will decide > what action to take. > -- > FreeBSD Core Team This seems to be a wanton violation of Article 19 of the Universal Declaration of Human Rights [1]. 1. https://www.un.org/en/universal-declaration-human-rights/ -- Igor M. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, May 12, 2019, 12:00 PM Eugene Grosbein wrote: > 12.05.2019 8:21, Warner Losh wrote: > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet > drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, > xe > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > > There are no 100M ed variants. There are some PC Card variants that have > 100M MII connections, but they are limited to about 12Mbps due to bus > limits. Even the PCI ones didn't have 100M mii connections. > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. > Not sure if ed(4) supports RTL8029AS. > It does, but there is the same limitations. The card can't do DMA, so it's limited by inb/outb limitations. It also only has a 10Mbps transceiver built in. If people sold 100M attachments, it still won't do much more than 10Mbps. Warner > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
v...@researchbsd.org wrote: > On Sun, May 12, 2019, at 7:50 PM, Sulev-Madis Silber wrote: > > On Friday, May 10, 2019, FreeBSD Core Team Secretary < > > core-secret...@freebsd.org> wrote: > > > The FreeBSD Core Team is aware of recent controversial statements made > > > on social media by a FreeBSD developer. We, along with the Code of > > > Conduct review committee, are investigating the matter and will decide > > > what action to take. Both the Core Team and the FreeBSD Foundation > > > would like to make it clear that views shared by individuals represent > > > neither the Project nor the Foundation. > > > > > > -- > > > FreeBSD Core Team > > > > > > > > > is this a political party?! i thought it was developer team of certain > > specific area server operating system? > > > > first, i would like to know if this is a joke? because it must be! then, if > > it's not, what has said and by who? > > > FreeBSD Core Team and the FreeBSD Foundation can claim injury to reputation. > We are waiting to see if they claim injury. > > âTort: a wrongful act, other than breach of contract, that results in > injury to another partyâs person, property, dignity, or reputation, and > which is recognized by statue or common law as a legitimate basis for > liability.â (2014, July 30). Retrieved from > https://www.youtube.com/watch?v=jQ6smN3lcnY > > Vester Not cc'd v...@researchbsd.org whois researchbsd.org : Creation Date: 2018-11-04T10:38:50.00Z Core is not a legal entity, just a mail list, can't sue. Foundation is in USA. Accused is not. USA law & morals not pre-emptive. Other countries have laws, courts & morals. Leave it to them & non tech lists. Orange haired person wrote lots of good code, an asset not to loose. Let's have current@ writeable only by subscribers as a mild troll deterent. Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
On Sun, May 12, 2019, at 7:50 PM, Sulev-Madis Silber wrote: > On Friday, May 10, 2019, FreeBSD Core Team Secretary < > core-secret...@freebsd.org> wrote: > > The FreeBSD Core Team is aware of recent controversial statements made > > on social media by a FreeBSD developer. We, along with the Code of > > Conduct review committee, are investigating the matter and will decide > > what action to take. Both the Core Team and the FreeBSD Foundation > > would like to make it clear that views shared by individuals represent > > neither the Project nor the Foundation. > > > > -- > > FreeBSD Core Team > > > > > is this a political party?! i thought it was developer team of certain > specific area server operating system? > > first, i would like to know if this is a joke? because it must be! then, if > it's not, what has said and by who? FreeBSD Core Team and the FreeBSD Foundation can claim injury to reputation. We are waiting to see if they claim injury. “Tort: a wrongful act, other than breach of contract, that results in injury to another party’s person, property, dignity, or reputation, and which is recognized by statue or common law as a legitimate basis for liability.” (2014, July 30). Retrieved from https://www.youtube.com/watch?v=jQ6smN3lcnY Vester ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
On Friday, May 10, 2019, FreeBSD Core Team Secretary <
core-secret...@freebsd.org> wrote:
> The FreeBSD Core Team is aware of recent controversial statements made
> on social media by a FreeBSD developer. We, along with the Code of
> Conduct review committee, are investigating the matter and will decide
> what action to take. Both the Core Team and the FreeBSD Foundation
> would like to make it clear that views shared by individuals represent
> neither the Project nor the Foundation.
>
> --
> FreeBSD Core Team
>
is this a political party?! i thought it was developer team of certain
specific area server operating system?
first, i would like to know if this is a joke? because it must be! then, if
it's not, what has said and by who?
was it like "i hate women" or "i don't recommend fbsd for this purpose"?
anyway, i'm not surprised if developers act strange on *social* media, as
they often behave what would be called inappropriate at best... that's why
they write code and don't sing on eurovision song contest, become elected
as president of the united states, or play on the newest marvel action
movie as a lead actor...
i know this, as i often act bad... sometimes i tell people which kind
mental disorders i have been diagnosed with ("only" asperger's syndrome, if
you're curious) as i often have problems of not understanding certain
social rules, which can't be fixed in any way, doesn't matter if people
insult me on how i did it again and how come i can't ever learn... sorry, i
really can't! each time it's surprise to me what happened...
i've used fbsd since v4.6, and despite having written some code already, i
don't really see myself becoming something like "official developer" if it
gives me this "extra butt" i could be kicked into if needed
also, if hans reiser in one day comes and wants to do something, do we turn
him down with like "sorry, you can't write code here, you killed your
wife"? really?
i think freebsd has enough purely technical disagreements that we don't
really need anything ELSE into this mix (like, what did the dev tweet last
night)
On Friday, May 10, 2019, FreeBSD Core Team Secretary <
core-secret...@freebsd.org> wrote:
> The FreeBSD Core Team is aware of recent controversial statements made
> on social media by a FreeBSD developer. We, along with the Code of
> Conduct review committee, are investigating the matter and will decide
> what action to take. Both the Core Team and the FreeBSD Foundation
> would like to make it clear that views shared by individuals represent
> neither the Project nor the Foundation.
>
> --
> FreeBSD Core Team
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
On Sun, May 12, 2019 at 03:16, Miroslav Lachman <000.f...@quip.cz> wrote: FreeBSD Core Team Secretary wrote on 2019/05/10 03:24: The FreeBSD Core Team is aware of recent controversial statements made on social media by a FreeBSD developer. We, along with the Code of Conduct review committee, are investigating the matter and will decide what action to take. Both the Core Team and the FreeBSD Foundation would like to make it clear that views shared by individuals represent neither the Project nor the Foundation. This is incredibly stupid and I am really sad to read things like this in the mailinglist of my favourite operating system (again). What will be next? Checking if developers do not smoke weed, drink alcohol or have sex without condom? https://yourlogicalfallacyis.com/slippery-slope Speaking freely does not mean you are entitled to having your speech published by any forum or mailing list. Having rules and enforcing them is good, every project has the right to enforce their rules in their spaces. The only problem here is that the "report" was posted by a known troll, so hopefully the outcome of the investigation is a) nothing, and b) mail from known anonymous email domains no longer gets accepted into mailing lists. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Core Team Response to Controversial Social Media Posts
On Sun, 12 May 2019 03:16:22 +0200 Miroslav Lachman <000.f...@quip.cz> wrote: > FreeBSD Core Team Secretary wrote on 2019/05/10 03:24: > > The FreeBSD Core Team is aware of recent controversial statements > > made on social media by a FreeBSD developer. We, along with the > > Code of Conduct review committee, are investigating the matter and > > will decide what action to take. Both the Core Team and the > > FreeBSD Foundation would like to make it clear that views shared by > > individuals represent neither the Project nor the Foundation. > > > This is incredibly stupid and I am really sad to read things like > this in the mailinglist of my favourite operating system (again). > What will be next? Checking if developers do not smoke weed, drink > alcohol or have sex without condom? > > "Be well, John Spartan" > > What's wrong with this world? > > I am from the country where totalitarian regime ruled for 40 years. I > was lucky to have seen freedom and lived freedom after the revolution > many years ago but now I am afraid that we have Thought Police even > in FreeBSD community. I never thought I'd live to fear again to speak > freely. +1 here, from another country which transitioned from 45 years of harsh totalitarian rule, through a brief period of relative freedom, to a more subtle form of a (thought) police superstate we happily live in today. Rest assured your worries about FreeBSD CoC enforcers are unfounded, though. Namely, last year several developers, including the one who is now being "investigated", orchestrated a lengthy rant on an internal ML targeting a population group based on race, sex, and sexual inclination, while invoking on EU convention on human rights protecting their right to do so. Neither the CoC comitte nor the Core team found that disturbing, probably as true believers to freedom of thought and speech. So, assuming they stick to their principles, I don't see why would they intervene now, particularly given that the developer has expressed his opinions outside of the project's MLs or other forums. Marko ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sat, 11 May 2019 20:21:46 -0500 Warner Losh wrote: > On Sat, May 11, 2019, 12:52 PM Eugene Grosbein wrote: > > > 11.05.2019 21:32, Julian H. Stacey wrote: > > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > > > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > More relevant questions might be 1) will these drivers only be removed from FBSD >= 13? 2) what versions of FBSD is Julian now running on his hardware? 3) does he ever plan to upgrade this hardware to >= FBSD 13? I know Julian and he has an amazing collection of old hardware. I suspect that most of it will not even be able to run FBSD 13. > > There are no 100M ed variants. There are some PC Card variants that have > 100M MII connections, but they are limited to about 12Mbps due to bus > limits. Even the PCI ones didn't have 100M mii connections. > -- Gary Jennejohn (gj@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipsec not working
Ok, thank you. 12.05.19 09:35, Kubilay Kocak пишет: On 12/05/2019 4:20 pm, Alexandr Krivulya wrote: Hi, after upgrading from r347050 to r347483 ipsec tunel on my notebook does not work any more. Connection is established as usual but no policies are installed. 2019-05-12 09:12:10 00[DMN] Starting IKE charon daemon (strongSwan 5.7.2, FreeBSD 13.0-CURRENT, amd64) 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Invalid argument 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv6 on port 4500 failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Protocol not available 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv4 on port 4500 failed ... 2019-05-12 09:12:10 01[CFG] selected proposal: ESP:AES_CBC_256/HMAC_SHA2_256_128/NO_EXT_SEQ 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI c96b2b97: Invalid argument (22) 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI cc951335: Invalid argument (22) 2019-05-12 09:12:10 01[IKE] unable to install inbound and outbound IPsec SA (SAD) in kernel 2019-05-12 09:12:10 01[IKE] failed to establish CHILD_SA, keeping IKE_SA See: https://svnweb.freebsd.org/changeset/base/347410 Ongoing thread: https://lists.freebsd.org/pipermail/svn-src-head/2019-May/124878.html ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipsec not working
On 12/05/2019 4:20 pm, Alexandr Krivulya wrote: Hi, after upgrading from r347050 to r347483 ipsec tunel on my notebook does not work any more. Connection is established as usual but no policies are installed. 2019-05-12 09:12:10 00[DMN] Starting IKE charon daemon (strongSwan 5.7.2, FreeBSD 13.0-CURRENT, amd64) 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Invalid argument 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv6 on port 4500 failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Protocol not available 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv4 on port 4500 failed ... 2019-05-12 09:12:10 01[CFG] selected proposal: ESP:AES_CBC_256/HMAC_SHA2_256_128/NO_EXT_SEQ 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI c96b2b97: Invalid argument (22) 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI cc951335: Invalid argument (22) 2019-05-12 09:12:10 01[IKE] unable to install inbound and outbound IPsec SA (SAD) in kernel 2019-05-12 09:12:10 01[IKE] failed to establish CHILD_SA, keeping IKE_SA See: https://svnweb.freebsd.org/changeset/base/347410 Ongoing thread: https://lists.freebsd.org/pipermail/svn-src-head/2019-May/124878.html ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ipsec not working
Hi, after upgrading from r347050 to r347483 ipsec tunel on my notebook does not work any more. Connection is established as usual but no policies are installed. 2019-05-12 09:12:10 00[DMN] Starting IKE charon daemon (strongSwan 5.7.2, FreeBSD 13.0-CURRENT, amd64) 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Invalid argument 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv6 on port 4500 failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: Protocol not available 2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed 2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Protocol not available 2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv4 on port 4500 failed ... 2019-05-12 09:12:10 01[CFG] selected proposal: ESP:AES_CBC_256/HMAC_SHA2_256_128/NO_EXT_SEQ 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI c96b2b97: Invalid argument (22) 2019-05-12 09:12:10 01[KNL] unable to add SAD entry with SPI cc951335: Invalid argument (22) 2019-05-12 09:12:10 01[IKE] unable to install inbound and outbound IPsec SA (SAD) in kernel 2019-05-12 09:12:10 01[IKE] failed to establish CHILD_SA, keeping IKE_SA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
