ok it does a 145 * 145 extra requests but hey, who cares !!
btw how can you trust the design advice of a site that has dark brown text on a lighter brown background and grey body text. awful, try reading that when you're over 65 and your eyes get 30% less contrast!
Even though saying that they had intelligence that Bin Laden planned to hijack domestic US planes... "Rice stressed that there was no way anyone could have predicted that terrorists would use hijacked planes as missiles and attack the World Trade Center and the Pentagon."
and yet:
TIME Magazine (Domestic edition), 'NEVER SAFE ENOUGH,' by Hugh Sidey, November 14, 1994 Volume 144, No. 20
During the cold war, when security agents used to play war games involving terrorist threats to the White House, the one unsolvable problem was a commercial airliner loaded with explosives working its way into the landing pattern at Washington National Airport, then veering off for a suicide plunge into the White House. The only answer was to shut down the airport, which Congress refused to consider, since its proximity and reserved parking spaces are prized legislative perks.
Cock waving which units you've had doesn't mask your ignorance.
have maps in it
tell you your heading
tell you where you've been
contain route information
GPS is a radio wave. Your receiver does the rest, calculating your distance from each of the satellites it receives said radio wave from. Anything else is provided by the capabilities of your receiver. In my case the facilities are as I specified. Long, lat, altitiude.
Forks spur competition. It is a bit like evolution. In nature, a new species
survives if the differentiation from the dominant group gives it an advantage for
survival in a hostile world. That is why the dinosaurs died out and the mammals
survived. Being big and powerful is not as important as being able to adapt to
changing conditions. Most of the time open source software succeeds, it is because
the end users are included in the process of building the software and making
decisions. It is inevitable then at some point there will be a divergence of views
and a decision has to be made. Sometimes it is not possible to make the right
decision as one does not have all the information and/or one's past experiences
have led to a certain opinion (which may not be necessarily right according
to others). This is fertile ground for a flame war and a fork.
Usually, it is possible that the fork will survive if it solves a pressing need
which was overlooked or addressed insufficiently by the core group.
Also in open source, after forks if one group is innovating more than the other
and taking the right decisions, it will also attract the userbase over a period
of time. The source code being freely available means one group can borrow ideas
from another. So the best ideas get replicated across the forks. Often it is also
seen that a particular developer is part of one or more projects (forks).
As many forks want to retain their own identity, there is more innovation for
differentiation from the other forks. Innovation is also due to the demands of
a specialized userbase (example - cryptographic implementations in OpenBSD
and implementation of ssh - OpenSSH). Now this leads to a positive feedback cycle
- all the good stuff gets picked up by everyone and everyone is free to experiment
more. An example in case are BSD variants - FreeBSD, NetBSD and OpenBSD. FreeBSD
and NetBSD use OpenSSH that has been developed by the OpenBSD team. The NetBSD
Packages collection pkgsrc has been ported to both FreeBSD and OpenBSD.
Forks also bring to notice some pressing need of the community when the lead
programmers/core team ignore them. Even Richard Stallman agreed to pursue the egcs
fork of gcc as the main branch for further development. Forks can sometimes be
"healed" and the codebases merged. The GCC/EGCS example above is a case in point.
Forks provide an opportunity for them to serve a specialised purpose while
being able to incorporate changes from the new branch.
It is possible that forks may hurt large corporations which like to be able to
control the direction of the product. This is the reason Sun will not release
Solaris 10 and Java under a OSS license. If at all they release the source
it will have some kind on a non-forking clause. Forks are always beneficial
to the end user in the long run, though they might cause a bit of pain initially.
Imposed control rather than concensus is central to the way big corporations
operate but not the way a good team of hackers operate. This is due to the
cathedral and bazaar model of development as described by Eric S Raymond.
Flame Wars
More often than not flame wars are precursor to forks - an indication that
all is not well within the project. Flame wars can also happen if a radical
new design or a drastic change to the project such as a license change or
replacing a subsystem with a better one. Flaring opinions and bruised egos
can damage the project but also enhance the project by hammering out new
ideas in a public discussion (because the discussion is public also means
the stakes are high). Bureaucracy and forced conformism
is detrimental to the growth of a project. But this is the way order has been
established in traditional companies. Flame wars and discussions are central to
the development of OSS to explore different design issues, but they also
harbor the potential to destroy the camaraderie in a project. It is
important that they be taken in the right spirit or the whole project
suffers. The reason why flame wars have go
Slashdot Mirror
super user
all powerfull login account
it's a design fault
garbage in, garbage out
you also forgot
<a href="/"
>click here</a>
did you notice the =) ?
The only right you are born with is death.
The key word is "arbitrary". The ability to load winsock.dll into mysql is dumb
You *could* compile against a set of headers to mark the dll as database server safe
You *could* compile against a set of headers to mark the dll as owned by the owner of a particular database
You could cryptographically sign the dlls and only accept signed dlls
"ooh but it's just sooo flexible"
just like activeX email
I wouldn't flout your ignorance like that, it's not becoming
that's right, dumbest
even when you redundantly explain it, it doesn't get any cleverer
arbitrary dlls == dumb
* If you do need to access a MySQL server from outside the same network, then you should definitely use something besides 3306.
yes, security through obscurity keeps you asleep at night
because on port 12345 no one will ever find it
mysql can load arbitrary dlls?
lol that's one of the dumbest features I ever heard!!
Particulary for applications like MySQL Linux is the OS of choice.
I love that, they DO go together rather well.
I hope you see the irony of that =)
I can't believe some of those windows freaks that are still out there call themselves professionals.
Linux : by amateurs, for amateurs.
almost there, try this :
A server should not have root accounts.
there, that's more like it
those who don't know unix
curl -f 'http://www.csszengarden.com/[001-146]/[001-146].
ok it does a 145 * 145 extra requests but hey, who cares !!
btw how can you trust the design advice of a site that has dark brown text on a lighter brown background and grey body text. awful, try reading that when you're over 65 and your eyes get 30% less contrast!
"no one could've predicted this"
... "Rice stressed that there was no way anyone could have predicted that terrorists would use hijacked planes as missiles and attack the World Trade Center and the Pentagon."
:
One such dumbshit is Condoleezza Rice
http://abcnews.go.com/US/story?id=90453&page=1/
Even though saying that they had intelligence that Bin Laden planned to hijack domestic US planes
and yet
TIME Magazine (Domestic edition), 'NEVER SAFE ENOUGH,' by Hugh Sidey, November 14, 1994 Volume 144, No. 20
During the cold war, when security agents used to play war games involving terrorist threats to the White House, the one unsolvable problem was a commercial airliner loaded with explosives working its way into the landing pattern at Washington National Airport, then veering off for a suicide plunge into the White House. The only answer was to shut down the airport, which Congress refused to consider, since its proximity and reserved parking spaces are prized legislative perks.
curl http://goatse.cx/hello.jpg | jpg2wav
"aghhhh, make me deaf NOW please! please! plase!"
When you say "we" please use "I", you can't speak for me.
or is
Cock waving which units you've had doesn't mask your ignorance.
GPS is a radio wave. Your receiver does the rest, calculating your distance from each of the satellites it receives said radio wave from. Anything else is provided by the capabilities of your receiver. In my case the facilities are as I specified. Long, lat, altitiude.
sed s'/<[^>]+>//g'
=)
Do YOU know what a GPS is ?
Mine doesn't do any of those things except determine my latitude, longitude and altitude from some satellites. It doesn't even have a screen !!
none of the above, really
they all suffer from design flaws, such as root/administrator
filesystems tied to the hardware
non-abstraction of simple things
didn't go with "everything is a file"
they all base their existence on one Computer / one OS thinking rather than being network centric
I'm sure you can think of other things
What OS would I be running now if Linus had just given up and said, "You're right"?
A good one (for my values of good =)
Forks spur competition. It is a bit like evolution. In nature, a new species survives if the differentiation from the dominant group gives it an advantage for survival in a hostile world. That is why the dinosaurs died out and the mammals survived. Being big and powerful is not as important as being able to adapt to changing conditions. Most of the time open source software succeeds, it is because the end users are included in the process of building the software and making decisions. It is inevitable then at some point there will be a divergence of views and a decision has to be made. Sometimes it is not possible to make the right decision as one does not have all the information and/or one's past experiences have led to a certain opinion (which may not be necessarily right according to others). This is fertile ground for a flame war and a fork.
Usually, it is possible that the fork will survive if it solves a pressing need which was overlooked or addressed insufficiently by the core group. Also in open source, after forks if one group is innovating more than the other and taking the right decisions, it will also attract the userbase over a period of time. The source code being freely available means one group can borrow ideas from another. So the best ideas get replicated across the forks. Often it is also seen that a particular developer is part of one or more projects (forks). As many forks want to retain their own identity, there is more innovation for differentiation from the other forks. Innovation is also due to the demands of a specialized userbase (example - cryptographic implementations in OpenBSD and implementation of ssh - OpenSSH). Now this leads to a positive feedback cycle - all the good stuff gets picked up by everyone and everyone is free to experiment more. An example in case are BSD variants - FreeBSD, NetBSD and OpenBSD. FreeBSD and NetBSD use OpenSSH that has been developed by the OpenBSD team. The NetBSD Packages collection pkgsrc has been ported to both FreeBSD and OpenBSD. Forks also bring to notice some pressing need of the community when the lead programmers/core team ignore them. Even Richard Stallman agreed to pursue the egcs fork of gcc as the main branch for further development. Forks can sometimes be "healed" and the codebases merged. The GCC/EGCS example above is a case in point. Forks provide an opportunity for them to serve a specialised purpose while being able to incorporate changes from the new branch.
It is possible that forks may hurt large corporations which like to be able to control the direction of the product. This is the reason Sun will not release Solaris 10 and Java under a OSS license. If at all they release the source it will have some kind on a non-forking clause. Forks are always beneficial to the end user in the long run, though they might cause a bit of pain initially. Imposed control rather than concensus is central to the way big corporations operate but not the way a good team of hackers operate. This is due to the cathedral and bazaar model of development as described by Eric S Raymond.
Flame Wars
More often than not flame wars are precursor to forks - an indication that all is not well within the project. Flame wars can also happen if a radical new design or a drastic change to the project such as a license change or replacing a subsystem with a better one. Flaring opinions and bruised egos can damage the project but also enhance the project by hammering out new ideas in a public discussion (because the discussion is public also means the stakes are high). Bureaucracy and forced conformism is detrimental to the growth of a project. But this is the way order has been established in traditional companies. Flame wars and discussions are central to the development of OSS to explore different design issues, but they also harbor the potential to destroy the camaraderie in a project. It is important that they be taken in the right spirit or the whole project suffers. The reason why flame wars have go
you are right
I think I was responding more to the AC than to you.
making a product that kicks the ass of your competitors
only if you choose that arena
This Open Graphics Card will kick the ass of its competitors as far as a lot of prospective purchasers are concerned, and I am one of them.
It won't be sat in my XP box running Half-Life but it will be sat in my terminal and get the hours and hours of use it hopefully will deserve.
2048x2048 and up - yay, now that's kicking ass.
Just like when you write a book and your editor just sends the manuscript to the printers.
Do you even know what an editor is ?
sigh, I doubt it.
Linux is cruft however you compile it.
For amateurs, by amateurs.