2. You're right that this is mainly a PR release- and though it doesn't flat-out say that this processor infringes on any MIPS patents, it's certainly implied. You seem to be strongly implying that this processor *doesn't* infringe on any MIPS patents. Do you have any facts about this, or is it your intuition?
A patent granted in USA is not automatically valid elsewhere, and you cannot infringe on a patent where it's not valid. The Chinese will infringe on MIPS patents if they try to export their chip to countries where the MIPS patens are valid.
Most users still have 32bit/33Mhz PCI bus, so they are limited by that as well.
Re:The real difference...
on
Why FreeBSD
·
· Score: 1
It took some while to remember that GNU sum takes a different parameter to emulate BSDs compared to its default behaviour (as if it is on a sysV). Linux is both and neither. Funnily enough, man sum won't tell you which one it defaults to.
The *BSD takes great pride in updated, informative and relevant man pages, in contrast some other systems that I shall not mention;-) One very good reason for using an OS is if it has excellent documentation, and here *BSD shines.
you know, Unix is by no means a dead OS, Mac OS X is based on BSD Unix, and so is Solaris.
you know, the grand parent poster is a "BSD is dead" troll, despite his comparatively low Slashdot ID. But this time he was unable to check the "Post Anonymously" before hitting Submit. It's well known that BSD-is-dead-trolls are feeble minded to to excessive inbreading, so his inability is understandable.
You asked about the difference as a desktop user between XFree86 and X.Org, and you got modded flamebait by some clueless moderator. How ironic that your sig says "#define CLUE 0".
What are the pros and cons between XFree86 and X.Org?
XFree86 changed their license last year, and this is the reason several *BSD and Linux distributions changed to X.Org. Xorg is based upon the latest unencumbered Free (just before XFree86 4.4), and developed from there.
Most users won't see much difference, yet, but XFree86 alienated many (most?) of their developers .
OpenBSD care more about free licenses than most, and they where less than pleased with the XFree86 license change; enough to include it in their
release song
but isn't this the sort of stuff that ANY network admin worth their salt should be completely aware of? If they need to be told this stuff they are not (IMHO) worth employing as other than apprentice network engineers. Or is this level of admin common in Windows environments?
Sure, where the employer can pay for it you'll have very good administrators, be it Windows or not.
On most smaller sites, the administrator is not a full-time administrator, and is doing administration ad-hoc to his real job. This usually means that he does not have much training in this, nor much time for it either. Now, with all these (useful) Plug-and-Play devices you are bound to have some problems.
If possible, restrict access by source IP address, limit the user accounts w/ SSH access, and don't allow remote root logins.
Another step to improve security if there are very few users is just to ONLY allow public key authentication. I've never seen such a box compromised remotely.
No kidding? By disallowing password authentication you've stopped the script kiddies dead in their tracks. As for disallowing root access, here are
some words from
an OpenBSD developer:
...
All unmitigated horseshit. Sorry. Look I use sudo, and I like it.
but it is no substitute for allowing root login to a box, and is no
substitute for "su", Sorry. They are different. I don't want to add a
billion sudoable local accounts to run boxen in a distributed
authentication environment. I want "root" local, and be done with it.
I want root exposed if someone knows the root password, not if someone
knows the root password or fourteen other idiot's passwords that are
used every day. That's not more secure. If you want a useful diff to
help stop this ridiculous discussion from propping up every little
while. Here's what I propose:....
Saying "don't login as root" is horseshit. It stems from the
days when people sniffed the first packets of sessions so logging in
as yourself and su-ing decreased the chance an attacker would see the
root pw, and decreast the chance you got spoofed as to your telnet host
target, You'd get your password spoofed but not root's pw. Gimme a
fucking break. this is 2005 - We have ssh, used properly it's secure.
used improperly none of this 1989 bullshit will make a damn bit of
difference.
-Bob
> > ASSUMING YOU EVER SEE IT. > > If you don't see a bug, you ship crap. > > > > That applies for both native and cross-built. THERE IS NO DIFFERENCE > AN UNSEEN BUG MAY BE THERE REGARDLESS. It has happened in the past to > OpenBSD and it may just happen again.
Seriously. You really don't see the correlation between using something and finding bugs? What planet are you from?
The Tribunal established by the Agreement referred to in Article 1 hereof for the trial and punishment of the major war criminals of the European Axis countries shall have the power to try and punish persons who, acting in the interests of the European Axis countries, whether as individuals or as members of organizations, committed any of the following crimes. The following acts, or any of them, are crimes coming within the jurisdiction of the Tribunal for which there shall be individual responsibility:
(a) Crimes against Peace: namely, planning, preparation, initiation or waging of a war of aggression, or a war in violation of international treaties, agreements or assurances, or participation in a Common Plan or Conspiracy for the accomplishment of any of the foregoing; (b) War Crimes: namely, violations of the laws or customs of war. Such violations shall include, but not be limited to, murder, ill-treatment or deportation to slave labor or for any other purpose of civilian population of or in occupied territory, murder or ill-treatment of prisoners of war or persons on the seas, killing of hostages, plunder of public or private property, wanton destruction of cities, towns, or villages, or devastation not justified by military necessity; (c) Crimes against Humanity: namely, murder, extermination, enslavement, deportation, and other inhumane acts committed against any civilian population, before or during the war,14 or persecutions on political, racial, or religious grounds in execution of or in connection with any crime within the jurisdiction of the Tribunal, whether or not in violation of domestic law of the country where perpetrated.
Leaders, organizers, instigators, and accomplices participating in the formulation or execution of a Common Plan or Conspiracy to commit any of the foregoing crimes are responsible for all acts performed by any persons in execution of such plan.
But hey, US has bullied most states/allies into agreements not extradite US citizens to the International Criminal Court. Of course, only low ranking service men/women are prosecuted in US for torture and other war crimes.
Re: Theo gave an interview to Forbes Mag. about Linux
From: Theo de Raadt (deraadtcvs.openbsd.org) Date: Fri Jun 17 2005 - 11:13:37 CDT
> On Fri, Jun 17, 2005 at 04:48:31PM +0200, J. Lievisse Adriaanse wrote: > > Theo gave an interview to Forbes Magazine, in which he stated: "It's > > terrible," De Raadt says. "Everyone is using it, and they don't > > realize how bad it is. And the Linux people will just stick with it > > and add to it rather than stepping back and saying, 'This is garbage > > and we should fix it.'" > > Heh. Theo never did pull his punches. I suppose there's now a war going > on in/. ?:)
If the Linux people actually cared about Quality, as we do, they would not have had as many localhost kernel security holes in the last year.
I've noticed that JavaScript enabled will cause Firefox to continously use 100% CPU and be unresponsive. One fix is to disable JavaScript and only enable it when needed. The culprit is ads served via JavaScript from kontera.com, so I just blackholed kontera.com.
As far as I understand, most FOSS software is avaliable under a BSD or GPL license, which are both copyrights. Accodring to this law, you can't download Linux, BSD, Firefox, OpenOffice, and the rest of our favorite FOSS software because it is copyrighted.
This is drivel in it's most refined and ignorant form.
The technical ignorance of the lawmakers worldwide is just appaling.
If the title were true, it'd really suck because then Swedes wouldn't be able to even look at any webpage because the Berne Convention (I assume y'all are a signatory nation) gives every work a copyright even if it's not officially registered.
Most of the new harsh laws (like this one, or the so called "anti-terrorist" "measurement", or software patents) are forced upon Europe from USA.
We don't don't need anymore self-righteous idiots running around the talk shows swinging their color-of-the-month light sabers. Bah... What's next? A Sith Lord running for President?
Interesting, I wondered who would still be throwing money at SCO. I believe I've spent my last dollar at McDonalds. I don't want to support a company that's still supporting SCO.
If you care about your health you should stay away from McDonalds, irrespective of their use of ancient SCO software.
"In a bid to be friendly with Open Source, SCO..." Just stop reading there.
OMG, if we, the savvy, sophisticated and informed/. readers should follow this in a consistent way, we would just about stop reading/. Hmh, is this why we have some dupes on the front page?
Java has it's uses, like any other programming language, along with it's disadvantages. C++ is very flexible and powerful (it supports several programming paradigms, appart from object oriented programming, for instance), but this comes at a price. Java seems rigid, very demanding on resources, and controlled to a large degree by Sun (witness the difficulties to get Sun Java running on *BSD). Yeah, there is the GPL version, but it's not up to par yet...
Slashdot Mirror
A patent granted in USA is not automatically valid elsewhere, and you cannot infringe on a patent where it's not valid. The Chinese will infringe on MIPS patents if they try to export their chip to countries where the MIPS patens are valid.
Not for single one usually, but add a few and do some networking on the shiny new 1GB NIC and it's not quite as shiny anymore.
Most users still have 32bit/33Mhz PCI bus, so they are limited by that as well.
The *BSD takes great pride in updated, informative and relevant man pages, in contrast some other systems that I shall not mention ;-) One very good reason for using an OS is if it has excellent documentation, and here *BSD shines.
you know, the grand parent poster is a "BSD is dead" troll, despite his comparatively low Slashdot ID. But this time he was unable to check the "Post Anonymously" before hitting Submit. It's well known that BSD-is-dead-trolls are feeble minded to to excessive inbreading, so his inability is understandable.
You asked about the difference as a desktop user between XFree86 and X.Org, and you got modded flamebait by some clueless moderator. How ironic that your sig says "#define CLUE 0".
XFree86 changed their license last year, and this is the reason several *BSD and Linux distributions changed to X.Org. Xorg is based upon the latest unencumbered Free (just before XFree86 4.4), and developed from there.
Most users won't see much difference, yet, but XFree86 alienated many (most?) of their developers .
OpenBSD care more about free licenses than most, and they where less than pleased with the XFree86 license change; enough to include it in their release song
Sure, where the employer can pay for it you'll have very good administrators, be it Windows or not. On most smaller sites, the administrator is not a full-time administrator, and is doing administration ad-hoc to his real job. This usually means that he does not have much training in this, nor much time for it either. Now, with all these (useful) Plug-and-Play devices you are bound to have some problems.
Sweet Jesus, I've forgotten how much iptables syntax sucks. The OpenBSD pf is much, much better than this.
Another step to improve security if there are very few users is just to ONLY allow public key authentication. I've never seen such a box compromised remotely.
No kidding? By disallowing password authentication you've stopped the script kiddies dead in their tracks. As for disallowing root access, here are some words from an OpenBSD developer:
If configured to do so, but you don't need to have dhcp to use an access point.
it generates a bunch of bits into files... the bits are the same AS LONG AS THE COMPILER IS THE SAME on all systems.
It doesn't run any of these bits so it doesn't NEED to have the build target hardware.
There was a recent thread about cross compiling on OpenbSD misc@. Perhaps this one summarize it nicely :
The current administration and Pentagon brass should read Charter of the International Military Tribunal
But hey, US has bullied most states/allies into agreements not extradite US citizens to the International Criminal Court. Of course, only low ranking service men/women are prosecuted in US for torture and other war crimes.
Theo de Raadt on Linux quality :
I've noticed that JavaScript enabled will cause Firefox to continously use 100% CPU and be unresponsive. One fix is to disable JavaScript and only enable it when needed. The culprit is ads served via JavaScript from kontera.com, so I just blackholed kontera.com.
This is drivel in it's most refined and ignorant form.
The technical ignorance of the lawmakers worldwide is just appaling.
Only appalling thing here is your ignorance.
Most of the new harsh laws (like this one, or the so called "anti-terrorist" "measurement", or software patents) are forced upon Europe from USA.
You mean this one?
You are misinterpreting the GP : The pictures are indecently decent, and thus the resounding "no no" on his workplace.
Of course, scapegoat is the major deciding factor here.....
OpenBSD installs into a "fake root" (you need root privs for this), and makes a package based upon this.
One day notice for "external" projects
If you care about your health you should stay away from McDonalds, irrespective of their use of ancient SCO software.
OMG, if we, the savvy, sophisticated and informed /. readers should follow this in a consistent way, we would just about stop reading /. Hmh, is this why we have some dupes on the front page?
Java has it's uses, like any other programming language, along with it's disadvantages. C++ is very flexible and powerful (it supports several programming paradigms, appart from object oriented programming, for instance), but this comes at a price. Java seems rigid, very demanding on resources, and controlled to a large degree by Sun (witness the difficulties to get Sun Java running on *BSD). Yeah, there is the GPL version, but it's not up to par yet...