Hmm, i had thought the green paint was some kind of safety color code or something... but know, knowing what it was, your are right - that would be quite useful. Long term maintenance costs would likely drop...
You know, RPM, deb, tgz, init, etc all had to start somewhere... if people didn't take working systems and replace/enhance them we would still be working off mainframes or worse.
This is a good idea, but I'm sure it will show to be very difficult. The neat thing about consoles is they are all the same, roughly, where PCs can be made up of pretty much any component you can find. On top of that, you have all sorts of software that can be present that have just as much as, or in some cases more than, hardware.
Previously, we've had self-sealing fuel tanks since WW2. But those had some weird lining that expanded to close the puncture. The important part is preventing burnoff and explosion, not so much leakage. If your venting fuel, you can still (as long as it's not huge) get to the ground safely.
That chromate conversion does sound awesome, but is that useful outside of cosmetic applications? (self-repairing bumpers and rims, anyone?)
If the WRK is the same as the real one, it has most likely had a thorough review and nitpicking before being releases - best not to make yourself look silly.
Having not seen the WRK, I harbor no opinion directly. I was just stating an alternative possibility.
As stupid and annoying as going through 6 ad-filled pages, that is entirely the publisher's choice to do, and working around it would be, while maybe not wrong, not nice. They pay for their bandwidth, and you have to admit that going to slashdot without ad support, would suck.
Not everyone is a cryptography expert. What needed to be done is someone to specifically state: "We shouldn't do this. Here's why:"
What appeared to have happened was a bunch of technical jabber completely skipping the security aspects, except for the one you quoted - which you must admit looks quite harmless and irrelevant - unless you understand fully what it means.
The ideal solution was that the maintainer(s) of the OpenSSL packages should have been watching for that kind of thing - after all, random patch submitters are not wrong in assuming the maintainer is a subject-matter-expert.
I don't fault the patch submitter. If you just plain don't know, theres nothing to really hold against you when there is supposed to be someone checking what you submit. I point fingers at the maintainer(s), but humans are only humans and mistakes happen. The important part is that it IS recoverable (pain-in-the-ass though it is) and, hopefully, it won't happen again.
I'm not disagreeing with that, but in this case we have (stretch it with me) a choice of Windows XP, Windows Vista, MacOSX, and 100x Linux distros.
In this case, yes there are too many choices. but would you rather have this spread: Windows Vista, MacOSX, OpenSUSE?
No. I would rather have to waste hours deciding which of the 100 linux distros to use. Even then, I would rather have the choice to decide between XP and Vista. To me, the freedom and flexibility having so many options provides, holds a higher priority than that of ease.
This philosophy carries with me into all kinds of ethical debates/conundrums, so it's a personality trait that I happen to be victim (or blessed) of. The point of this last bit here is, there are people who want these choices. If you don't want them, ignore them - or find some way (even arbitrary!) to filter them.
Oh, I was wrong about the "64-bit pure" part. Slamd64 is a multilib. If you want a pure variant, you may want bluewhite64 (which indeed already released 12.1, as of today)
Problem solved, you are now in a shell with UID/GID of 0.
That said, I am now pulling down all the torrents (and I'll seed with my whopping 20k/s upload throughput). Can't wait for slamd64 to put 12.1 out! (64-bit pure slackware variant)
Slashdot Mirror
I meant worse as on "old" - if we didn't take chances and rework/invent stuff we would be very very far behind where we are now.
Hmm, i had thought the green paint was some kind of safety color code or something... but know, knowing what it was, your are right - that would be quite useful. Long term maintenance costs would likely drop...
You know, RPM, deb, tgz, init, etc all had to start somewhere... if people didn't take working systems and replace/enhance them we would still be working off mainframes or worse.
This is a good idea, but I'm sure it will show to be very difficult. The neat thing about consoles is they are all the same, roughly, where PCs can be made up of pretty much any component you can find. On top of that, you have all sorts of software that can be present that have just as much as, or in some cases more than, hardware.
Previously, we've had self-sealing fuel tanks since WW2. But those had some weird lining that expanded to close the puncture. The important part is preventing burnoff and explosion, not so much leakage. If your venting fuel, you can still (as long as it's not huge) get to the ground safely.
That chromate conversion does sound awesome, but is that useful outside of cosmetic applications? (self-repairing bumpers and rims, anyone?)
That didn't make much sense... not the right context for that (lame) joke.
No, all I'm saying is this:
If the WRK is the same as the real one, it has most likely had a thorough review and nitpicking before being releases - best not to make yourself look silly.
Having not seen the WRK, I harbor no opinion directly. I was just stating an alternative possibility.
That works the other way too... the real windows kernel could be full of shit, and they would look better for the review of the WRK.
That was hardly a reference to porn. Grow up.
I don't think that was a joke...
Embassy / consulate. They might not let you through customs, but I imagine it's another thing entirely to prevent someone from entering one of those.
You don't stand alone.
As stupid and annoying as going through 6 ad-filled pages, that is entirely the publisher's choice to do, and working around it would be, while maybe not wrong, not nice. They pay for their bandwidth, and you have to admit that going to slashdot without ad support, would suck.
Your Mac uses CUPS. Pop open your Mac and go to http://localhost:631/ and you will see.
Not everyone is a cryptography expert. What needed to be done is someone to specifically state: "We shouldn't do this. Here's why:"
What appeared to have happened was a bunch of technical jabber completely skipping the security aspects, except for the one you quoted - which you must admit looks quite harmless and irrelevant - unless you understand fully what it means.
The ideal solution was that the maintainer(s) of the OpenSSL packages should have been watching for that kind of thing - after all, random patch submitters are not wrong in assuming the maintainer is a subject-matter-expert.
I don't fault the patch submitter. If you just plain don't know, theres nothing to really hold against you when there is supposed to be someone checking what you submit. I point fingers at the maintainer(s), but humans are only humans and mistakes happen. The important part is that it IS recoverable (pain-in-the-ass though it is) and, hopefully, it won't happen again.
Web2.0 doesn't really have anything to do with "the internet". Web2.0 just has to do with a small subset of protocols and applications.
The internet is just a smidgen bigger than www.
They didn't "download warez" - they released them. You know, ripped and cracked it, wrote the NFO, and posted it up on usenet?
A granny symbol!
I'm not disagreeing with that, but in this case we have (stretch it with me) a choice of Windows XP, Windows Vista, MacOSX, and 100x Linux distros.
In this case, yes there are too many choices. but would you rather have this spread: Windows Vista, MacOSX, OpenSUSE?
No. I would rather have to waste hours deciding which of the 100 linux distros to use. Even then, I would rather have the choice to decide between XP and Vista. To me, the freedom and flexibility having so many options provides, holds a higher priority than that of ease.
This philosophy carries with me into all kinds of ethical debates/conundrums, so it's a personality trait that I happen to be victim (or blessed) of. The point of this last bit here is, there are people who want these choices. If you don't want them, ignore them - or find some way (even arbitrary!) to filter them.
I would rather have too many choices, than 2 or 3 bad ones.
And then, Par2 came along, and allowed more flexibility.
We still use them, on usenet anyways.
Oh, I was wrong about the "64-bit pure" part. Slamd64 is a multilib. If you want a pure variant, you may want bluewhite64 (which indeed already released 12.1, as of today)
Need root? "sudo su".
Problem solved, you are now in a shell with UID/GID of 0.
That said, I am now pulling down all the torrents (and I'll seed with my whopping 20k/s upload throughput). Can't wait for slamd64 to put 12.1 out! (64-bit pure slackware variant)
Not everyone can "direct it towards building a better product." We do what we can, and if that means crying foul and bitching, so be it.
Probably on SBC's side, as they are having a (smaller) issue with the link(s) to Sprint.