[23 years]... a major milestone for any free software or open-source software project
gcc, 1987, ~30 years old
X11, 1987, ~29 years old.
GNU HURD, 1990, ~27 years old (and lol)
Linux (kernel) 1991, ~26 years old
386BSD -> NetBSD and FreeBSD, 1992, 1993; ~25 years old
I think you need to use the HTML entities: £ € ¥
Because otherwise they turn out like this: £ â Â¥
With HTML you get: £ € ¥
No, I didn't use HTML entitles. I'm on a Mac. I just used the 'Show Emoji & Symbols' pulldown menu to enter them.
/. likes some things, e.g. £ € ¥ é ü ñ. Most of the other things I might use – degree sign, thorn, eth, certain accented characters – don't work whether I enter them directly, from Show Emoji & Symbols, or as HTML entities.
One thing we definitely don't need are "helpful" comments like this from the peanut gallery.
Ahh, the good old snobby, elitist, holier than thou, "fuck your suggestions, it's open source,
Coming from a snobby elitist holier than thou "do what I tell you and shut the fuck up". The irony is so thick you can cut it with a knife.
We already know we need to do stuff like run fuzzers. Suggestions like that are not the least bit helpful you stupid dumbfuck.
When people have constructive contributions they want to give us, we help them integrate them. When nitwits like you shout at us from the peanut gallery we ignore you.
...perhaps OpenVPN should consider adding fuzzing to their internal security analysis in the future."
This is FOSS software. If someone is doing fuzzing testing, they should jump in and contribute it. I can't imagine that the OpenVPN project, or any other FOSS software project would say no to such a contribution.
Those who stand around and offer lame suggestions like "$project should do this" are useless IMO.
I'm currently paid to work on FOSS software. There's a lot of things we need to do. There aren't enough resources to do all of them. One thing we definitely don't need are "helpful" comments like this from the peanut gallery.
Meh, RCN were supposed to come to my town. They signed an agreement with the town. Then they reneged when the economy tanked in 2001 or 2008 (I forget which). The town didn't negotiate any penalty clause, so RCN just walked away.
We do have Comcast and Verizon FIOS, not that that has made either of them more competitive, nor do I have any proof that if RCN had come that prices would be any different than they are now.
Regardless, RCN's name is mud AFAIC, right down there with Comcast and FIOS..
I guess my day job is safe – for the time being – from being taken over by AIs. My retirement plan to be a Ms. Pacman champ seems to be in jeopardy though. Time to rethink.
I'm issued a boarding pass when I check in. Somewhere there's an e-ticket, possibly in the email confirmation I received after purchasing. I haven't seen a ticket in years.
This will create a huge demand for rental businesses....rent [and] return at the destination airport....This could be expanded easily to laptops...
I'm not sure how that helps people who want a laptop to use after they leave the airport. Like most, I take my laptop on business trips, because I'm going to use it to work at my destination.
I actually almost never use my laptop on board the plane. And I don't trust leaving it in checked baggage.
Wait. Regulatory burdens put in place why exactly? Because without those nasty old regulatory burdens the industry destroyed the environment, shifting the real cost of that source of energy to the future , as costs to clean up the messes they made.
Costs that in many cases were born by everyone, not just the people who mined that coal, or burned it.
And then everyone said no, not any more you don't. And on top of that we place a dollar value preserving the environment.
Basically pure, unfettered capitalism all the way around is what has destroyed coal in the Appalachians.
But you want a Communist solution. You want everyone – everyone – to pitch in and make sure you have a good paying job.
The Constitution doesn't guarantee you a job. There's no Amendment for that. You want Capitalism. You live by Capitalism. You die by Capitalism. Go join the buggy whip and candle makers.
Or learn something new to make a living with.
In times of profound change the learners inherit the Earth, while the learned find themselves beautifully equipped to deal with a world that no longer exists. – Al Rogers
In times of drastic change, it is the learners who inherit the future. The learned usually find themselves equipped to live in a world that no longer exists. – Eric Hoffer
Pretty much everything new starts as a fork, to some degree; it doesn't mean the plan is to maintain a fork - simply that the fork hasn't been merged into the kernel yet.
Another yeahthanx. Tell us something we don't know. How long has this fork been around already? How much is already upstream?
Getting the code merged into the Kernel is a process, and will take time (several months at a minimum -- and probably longer, unless the code is magically perfect out of the gate). Are developers and designers supposed sit on their thumbs until then?
Yeah. Guess what part of my job is. I know exactly what's involved and how long it takes. And I've seen plenty of kernel forks that are going nowhere. Ever. Because a) getting into the mainline kernel isn't even on their radar; or b) they want to wait until they're done and think it's perfect; or c) they're too embarrassed to show their work, piecewise, to kernel devs.
But once they've got a giant blob of code that's too big for anyone to digest, it's already too late. Or by then there's five different RISCV ports, all different, and nobody wants to do the work to make a common code base.
So they settle for getting a fork running, and once it's running, they're so proud of it they dump the code on a web site, announce Achievement Unlocked, and they're on to whatever the next thing is.
Sitting around on thumbs is not required. Ironically, most software devs have multiple things they can work on. And if you're diligent, there isn't that much waiting.
I stand by my original statement: Forks of the kernel aren't newsworthy – getting it into the mainline kernel is the only thing that's interesting.
Yeahthanx. I've been using BSD since 386BSD 0.1 (and Linux/Slackware since circa 1994) but this is about forking the Linux kernel. FreeBSD isn't just not the answer, it's so far out in right field even a southpaw batter isn't going to hit there – ever.
The right approach is to get involved with the upstream kernel community and get the changes they need into the kernel. Forking just means it'll always be on the sideline.
Availability of a low cost SoC – a la RaspPi3, Pine64, or ExpressoBin – would be good too.
GPL is the GNU Public License, not, as the OP claims, the GNU Protective License.
Compiling with gcc does not infect your source. You might be required to release your source for other reasons, but not because you compiled it with gcc. Their lawyers are mistaken. And even if you wanted to be ultra conservative and believe the lawyers anyway, you can always compile with clang, or Intel's icc, or AMD's acc to get around that.
Finally, the GPL doesn't require you to give source to everyone. You only have to give it to people who ask for it. Let's say you build a system for Dewey Cheatham and Howe. If they're the only ones who know about it, and they're the only ones who could ask for it. If you put your software your software on a web site for download only then would anyone know about it and be able to ask for the source
No, IANAL. But I've been working with FOSS and the GPL for 25 years, so I know a little something about it. In the end though it's always what your own lawyer tells you that matters. So get a lawyer and pay for your legal advice.
Slashdot Mirror
Aw shucks. I would have modded you Funny except I already posted in this thread.
Get rid of them in 2020!
Fortune favors the bold.
[23 years] ... a major milestone for any free software or open-source software project
gcc, 1987, ~30 years old
X11, 1987, ~29 years old.
GNU HURD, 1990, ~27 years old (and lol)
Linux (kernel) 1991, ~26 years old
386BSD -> NetBSD and FreeBSD, 1992, 1993; ~25 years old
But 23 years is a nice accomplishment.
Burroughs
I dare say if she'd hit him in the book with a frying pan, he'd still be alive to talk about it.
And how many deaths by frying pans are there every year, in say, England?
$ € £ What's the issue?
I think you need to use the HTML entities: £ € ¥
Because otherwise they turn out like this: £ â Â¥
With HTML you get: £ € ¥
No, I didn't use HTML entitles. I'm on a Mac. I just used the 'Show Emoji & Symbols' pulldown menu to enter them.
/. likes some things, e.g. £ € ¥ é ü ñ. Most of the other things I might use – degree sign, thorn, eth, certain accented characters – don't work whether I enter them directly, from Show Emoji & Symbols, or as HTML entities.
$ € £ What's the issue?
Ahh, the good old snobby, elitist, holier than thou, "fuck your suggestions, it's open source,
Coming from a snobby elitist holier than thou "do what I tell you and shut the fuck up". The irony is so thick you can cut it with a knife.
We already know we need to do stuff like run fuzzers. Suggestions like that are not the least bit helpful you stupid dumbfuck.
When people have constructive contributions they want to give us, we help them integrate them. When nitwits like you shout at us from the peanut gallery we ignore you.
In case you were wonder why we're ignoring you
...perhaps OpenVPN should consider adding fuzzing to their internal security analysis in the future."
This is FOSS software. If someone is doing fuzzing testing, they should jump in and contribute it. I can't imagine that the OpenVPN project, or any other FOSS software project would say no to such a contribution.
Those who stand around and offer lame suggestions like "$project should do this" are useless IMO.
I'm currently paid to work on FOSS software. There's a lot of things we need to do. There aren't enough resources to do all of them. One thing we definitely don't need are "helpful" comments like this from the peanut gallery.
Meh, RCN were supposed to come to my town. They signed an agreement with the town. Then they reneged when the economy tanked in 2001 or 2008 (I forget which). The town didn't negotiate any penalty clause, so RCN just walked away.
We do have Comcast and Verizon FIOS, not that that has made either of them more competitive, nor do I have any proof that if RCN had come that prices would be any different than they are now.
Regardless, RCN's name is mud AFAIC, right down there with Comcast and FIOS..
The ability – financially – to deploy the ground-based network to support cellular.
IMO there's no way we could have done anything with the spectrum.
... a tiny angle error...
I'm not saying mistakes don't happen (think Viking 1 antenna adjustment) but we have a pretty good record for not making tiny angle errors.
And as others have pointed out, the relative velocity isn't anywhere near the rates you cited. (and great way to mix KM and MPH).
Personally I think you're being just a teeny bit alarmist.
What? You don't think AIs want to have fun too?
I guess my day job is safe – for the time being – from being taken over by AIs. My retirement plan to be a Ms. Pacman champ seems to be in jeopardy though. Time to rethink.
And if my company issued laptop is stolen from checked baggage – on business travel – my company will just have to suck it up I guess.
Would Twitler listen if all 500 of the Fortune 500 company CEOs told him it's a bad idea?
After every trip I'll just wipe it and reinstall. I don't keep anything of value on it anyway – the time it takes to do that is pretty negligible.
I'm issued a boarding pass when I check in. Somewhere there's an e-ticket, possibly in the email confirmation I received after purchasing. I haven't seen a ticket in years.
This will create a huge demand for rental businesses....rent [and] return at the destination airport....This could be expanded easily to laptops...
I'm not sure how that helps people who want a laptop to use after they leave the airport. Like most, I take my laptop on business trips, because I'm going to use it to work at my destination.
I actually almost never use my laptop on board the plane. And I don't trust leaving it in checked baggage.
Also compiled fine on Fedora 25 box w/ gcc-6.3.1 and Ubuntu yakkety w/ gcc-6.2.0.
Built fine on my Mac.
I did have to comment out the "LIBS=-lrt" line at the top of the Makefile, and there were a handful of warnings.
(LLVM 8.1.0, clang-802.0.42)
Where's the "-1 You're an Idiot" downvote?
Nowhere did OP say anything about Polacks. But you nicely filled in the missing bits.
(And yes, when I first heard the joke – about a million years ago – it was the Polish Space Agency going to the Sun at night.)
54 out of 100 Senators and 234 out of 435 Representatives, and Twitler don't.
The numbers don't line up.
...try to put them on a steak...
Huh?
Who puts tomatoes on steak? (I have seen people put ketchup on a steak. WTF.
Wait. Regulatory burdens put in place why exactly? Because without those nasty old regulatory burdens the industry destroyed the environment, shifting the real cost of that source of energy to the future , as costs to clean up the messes they made.
Costs that in many cases were born by everyone, not just the people who mined that coal, or burned it.
And then everyone said no, not any more you don't. And on top of that we place a dollar value preserving the environment.
Basically pure, unfettered capitalism all the way around is what has destroyed coal in the Appalachians.
But you want a Communist solution. You want everyone – everyone – to pitch in and make sure you have a good paying job.
The Constitution doesn't guarantee you a job. There's no Amendment for that. You want Capitalism. You live by Capitalism. You die by Capitalism. Go join the buggy whip and candle makers.
Or learn something new to make a living with.
In times of profound change the learners inherit the Earth, while the learned find themselves beautifully equipped to deal with a world that no longer exists. – Al Rogers
In times of drastic change, it is the learners who inherit the future. The learned usually find themselves equipped to live in a world that no longer exists. – Eric Hoffer
Pretty much everything new starts as a fork, to some degree; it doesn't mean the plan is to maintain a fork - simply that the fork hasn't been merged into the kernel yet.
Another yeahthanx. Tell us something we don't know. How long has this fork been around already? How much is already upstream?
Getting the code merged into the Kernel is a process, and will take time (several months at a minimum -- and probably longer, unless the code is magically perfect out of the gate). Are developers and designers supposed sit on their thumbs until then?
Yeah. Guess what part of my job is. I know exactly what's involved and how long it takes. And I've seen plenty of kernel forks that are going nowhere. Ever. Because a) getting into the mainline kernel isn't even on their radar; or b) they want to wait until they're done and think it's perfect; or c) they're too embarrassed to show their work, piecewise, to kernel devs.
But once they've got a giant blob of code that's too big for anyone to digest, it's already too late. Or by then there's five different RISCV ports, all different, and nobody wants to do the work to make a common code base.
So they settle for getting a fork running, and once it's running, they're so proud of it they dump the code on a web site, announce Achievement Unlocked, and they're on to whatever the next thing is.
Sitting around on thumbs is not required. Ironically, most software devs have multiple things they can work on. And if you're diligent, there isn't that much waiting.
I stand by my original statement: Forks of the kernel aren't newsworthy – getting it into the mainline kernel is the only thing that's interesting.
Yeahthanx. I've been using BSD since 386BSD 0.1 (and Linux/Slackware since circa 1994) but this is about forking the Linux kernel. FreeBSD isn't just not the answer, it's so far out in right field even a southpaw batter isn't going to hit there – ever.
...there's already a fork of Linux for RISC-V.
Wrong approach.
The right approach is to get involved with the upstream kernel community and get the changes they need into the kernel. Forking just means it'll always be on the sideline.
Availability of a low cost SoC – a la RaspPi3, Pine64, or ExpressoBin – would be good too.
Why was this voted -1? Very informative.
Maybe because it's factually incorrect.
GPL is the GNU Public License, not, as the OP claims, the GNU Protective License.
Compiling with gcc does not infect your source. You might be required to release your source for other reasons, but not because you compiled it with gcc. Their lawyers are mistaken. And even if you wanted to be ultra conservative and believe the lawyers anyway, you can always compile with clang, or Intel's icc, or AMD's acc to get around that.
Finally, the GPL doesn't require you to give source to everyone. You only have to give it to people who ask for it. Let's say you build a system for Dewey Cheatham and Howe. If they're the only ones who know about it, and they're the only ones who could ask for it. If you put your software your software on a web site for download only then would anyone know about it and be able to ask for the source
No, IANAL. But I've been working with FOSS and the GPL for 25 years, so I know a little something about it. In the end though it's always what your own lawyer tells you that matters. So get a lawyer and pay for your legal advice.