OpenPIC has been supported by linux for quite a while now as it is the SMP scheme used on SMP PowerPC boards. Do a search in linux/arch/ppc for openpic.
-----------------------------------------------
Opinion/AFAIK:
in theory any CPU can be used in an SMP configuration. The reason intel's newer Celeron's don't is that Intel's APIC scheme has moved a lot of the PIC logic onto the CPU core - IRQ control logic is split between an IO-APIC on the motherboard and a PIC on the CPU core (connected by a special PIC bus. Traditionally the PIC is external to the core.
intel just disable the more advanced SMP PIC logic on Celerons. It's still there, it just can't talk to other CPU's. Still, in theory, even these crippled CPU's could still run in SMP with a special motherboard that implemented a totally external PIC. (just wouldn't be Intel's SMP scheme).
AFAIK OpenPIC is totally external to the CPU, so it does not need explicit CPU support. So the K6 *could* have been run in SMP config *if* someone had made a K6 OpenPIC board.
But the extensibility of it is GOOD. It is it's major strongpoint. Extensibility in X was not a hack, it was a central design goal, and engineered into X from the outset! It is the reason why X is such a durable protocol and why we should keep X.
Sure X has a couple of ugly bits. So let's fix it. Like i said in the reply above - don't throw the baby out with the bath water - cause the core of X is extremely well thought out, well designed and easily capable of providing everything we need.
Why oh why oh why do so many people harp on here on slashdot that X is 'bad'? Do you even understand the issues? Have you even ever tried comparing X with other windowing systems? Do you have any idea of the design goals of X?
In short, do the people who post "X sucks let get rid of it!" to threads like this have ANY feckin' clue?
"It's slow - lets get rid of it!!!": Is it really slow? Seems fast enough to me, and I started out with X11R6 on Sparcstation 1's. Perhaps you are confusing X with XFree86?
Also, most other windowing systems have a huge advantage over X, ie they are called as library or system functions, whereas X was designed as a PROTOCOL for network transparency. This has an impact on speed but only slight, and if the X client and server are running on the same host there is no reason why they can't communicate via shared memory or some other X extension (see below). However X has something that these procedure call window systems don't: SEAMLESS network transparency. If I show you my desktop you have absolutely no way to tell which windows are running locally and which are running on various other machines round here.
"It's bloated! lets get rid of it!":
What is bloated exactly? X the protocol is a very lean protocol (though very chatty), designed with extensibility and low-latency connections in mind. ie if you can't do it with X, then go write an EXTENSION. Implementations are a different story, but again X != XFree86. (though XF4 is a different story - leaner and faster).
If the implementation you use is bloated go use a different one. Have a look at handhelds.org they're working on a small footprint X server for handhelds.
"Xlib/Xt suck!! let's get rid of X!":
Then don't use Xlib or Xt! Use Qt or GTK+.
"X sucks for fonts. let's get rid of it!":
Firstly, I bet you havn't read the X-Font-Deuglification HOWTO. Go to linuxdoc.org/HOWTO and read it and find out how to make all those sites like microsoft.com, dabs.com, etc, look right under netscape. Don't blame X cause it wasn't setup right! Blame your Vendor.
Secondly, X apparently won't handle anti-aliasing of fonts as it stands now. ("So let's get rid of it!"). HOWEVER do you know why anti-aliasing of fonts was invented? Cause in the mists of time, a lot of computers had terrible resolution screens. Anti-aliasing is a HACK to make fonts look better, nowadays we nearly all have at least 100dpi displays so you are better off setting X up CORRECTLY and getting clear fonts without anti-aliasing.
Thirdly, if there truly is a problem with font handling in X, well then let's do something about this small problem. Either implement an extension (Display Postscript springs to mind - most commercial Unices have this), or else fix X if needs be so that X11R7 has even better font handling.
In Summary:
X is one of the most amazing software concepts ever! It's like Unix, a timeless classic.
- If it can't do something, extend it! - If it has a limitation, then get it fixed for the next major release of the X protocol!
but please stop the silly misinformed whinging and whineing.
considering the whole point of MySQL is to sacrifice the heavier features of SQL and 'Enterprise' RDBM's in the quest for speed, it'd be amazing if it wasn't faster than Oracle.
What would you say makes a cluster a/Beowulf cluster/, as opposed to just a bunch of computers running linux linked by ethernet? What is it that differentiates the Beowulf cluster from the rest?
Re:Recompile IRIX kernel -- yes you do!
on
New Mega Alphas
·
· Score: 1
"configured at boot time" == kernel relinked at boot time == just like IRIX, Tru64[1], Solaris, UnixWare...
Get over it.. just about every Unix has to recompile the kernel for hardware/kernel config changes, just like linux.
1. Yes, there are other DNS servers, but BIND must surely be the most widely used on the 'net.
2. I am trying to correct your mistaken belief that DNS servers don't push zone changes.
A BIND 8 slave will/immediately/ fetch the updated zone when it recieves the notify from the master, irregardless of whether any client asked for a record or not, and irregardless of whether it still has records cached that havn't expired yet.
Also, DNS NOTIFY is part of the DNS spec, so other servers are free to implement it.
"If a change is made, and *your* server has cached records, it won't know about the changes until the records expire"
BIND 8 has a notify mechanism whereby the master informs the other listed NS's if a zone changes.
edit the serial number on a zone and do ndc reload zone. then watch the logs as your server notifies the slaves.. then seconds later watch as named reports loads of zone transfers..
Comparing MS qualifications to commercial pilots qualifications is wrong..
Firstly a commercial pilot needs a generic licence, an ATPL, which needs a lot of training, at the end of which you/don't/ get your qualification - you need to go get some real experience first. (it's probationary).
As for individual aeroplanes, well there's no question of a type rating for a 737 being valid for a 757 - type ratings aren't even valid across different versions of the same plane sometimes. That'd be ludicrous. And type ratings differ from MS quals enormously in that they are regulated, eg by the FAA in the states, CAA in the UK, DoT in Ireland. The type rating has nothing to do with the vendor of the plane. (they might have had input into the requirements for the type-rating.) Also, once you have a type rating, you can stay current by getting checked out every 6 months by an instructor with the appropriate instructors type rating, and you can stay current on as many different type-ratings as you want, if you can find the time on the planes and an intructor for it.
So comparing a regulated, safety orientated, non-vendor locked, rigorous licencing scheme to a proprietary, vendor-locked, marketing orientated certification programme is mad.
(unless you want to argue that computer training should be regulated and licenced?)
the point is that this gives you complete remote access to your machine.. you have a rack of servers, you put a terminal server in and the wire all the machines into it, then you can remote boot your pc servers by telneting or dialling into the term server.
CPQ has had this for a while now (Insight something). It used to be a card (with a 386 on it), but now it's integrated in most new proliant servers, you just enable it in Compaq's config utility.
It was not MS that gave up - it was Compaq!!!! Compaq decided to drop support for NT on Alpha!!
Who do you think had to maintain Alpha/NT? Clue: Not MS. Yes, DEC/Compaq had to pay for a complete NT software development dept., because DEC/Compaq had to do the maintenance. (same thing when NT used to run on PPC - IBM had to maintain it, until they realised it didn't sell).
Then some bright spark looked at the figures and realised that nobody was buying NT on Alpha. It's best marketshare was on workstations - ~15%!! On servers it was even worse - because people who tend to buy nice hardware like Alpha also tend to buy nice OS's like OpenVMS or Unix. People were not spending money on Alpha/NT.
They put 2 and 2 together and realised that paying for NT/Alpha was costing more than the revenues generated by Alpha/NT sales. And that's why it was scrapped. The biggest money maker on Alpha is Unix, closely followed by VMS.
Also, look how hard compaq is pushing Linux on Alpha. This is for the same reason as why NT was dropped - money. Linux sells a lot of Alpha's.. esp in the lower end, eg Linux marketshare on DS10's is about 40% or higher... it also does well on clusters. And Compaq is pushing linux/alpha clusters really hard.
(my mouse mat is a picture of tux on a fat motorcycle with the Compaq Alpha logo, and a banner saying "Linux SCREEEEAMMMS on Compaq Alpha".. this is an official compaq mousemat)
:)
in fact this Alpha cluster will most likely run linux..
While you are right that narrow/wide has 8/16 target ID's, that does not neccessarily mean you can plug 7/15 devices onto a SCSI bus.
Eg, Ultra will not really tolerate more than 4 devices on a bus. It's possible to have 5 or 6 Ultra devices on the same bus, but you are likely to have problems.
ermmm.. actually a lot of Win software did use to have the "Regents of California" coyright statement. Eg ftp on older WinXX installs would print it out when you started it. (code had to actually print it out to the user - nothing to do with code comments)
However the "must display copyright" clause was removed from the BSD licence about a year or 3 ago. I believe it was RMS that persuaded them. Hence the reason why you can't find "Regents..." in WinXX today. But still that code is BSD based - eg the WinXX tcp/ip stack was developed from BSD. A lot of the utilities (ftp, traceroute, etc.) are BSD based.. etc..
Slashdot Mirror
Fact:
OpenPIC has been supported by linux for quite a while now as it is the SMP scheme used on SMP PowerPC boards. Do a search in linux/arch/ppc for openpic.
-----------------------------------------------
Opinion/AFAIK:
in theory any CPU can be used in an SMP configuration. The reason intel's newer Celeron's don't is that Intel's APIC scheme has moved a lot of the PIC logic onto the CPU core - IRQ control logic is split between an IO-APIC on the motherboard and a PIC on the CPU core (connected by a special PIC bus. Traditionally the PIC is external to the core.
intel just disable the more advanced SMP PIC logic on Celerons. It's still there, it just can't talk to other CPU's. Still, in theory, even these crippled CPU's could still run in SMP with a special motherboard that implemented a totally external PIC. (just wouldn't be Intel's SMP scheme).
AFAIK OpenPIC is totally external to the CPU, so it does not need explicit CPU support. So the K6 *could* have been run in SMP config *if* someone had made a K6 OpenPIC board.
(PIC == programmable interrupt controller)
errmmm... it's being released under GPL and LGPL. So tell me: what's to stop people from creating ksoffice?
the opening of Soffice benefits KDE too.
20 years? X was only born 14 years ago..
But the extensibility of it is GOOD. It is it's major strongpoint. Extensibility in X was not a hack, it was a central design goal, and engineered into X from the outset! It is the reason why X is such a durable protocol and why we should keep X.
Sure X has a couple of ugly bits. So let's fix it. Like i said in the reply above - don't throw the baby out with the bath water - cause the core of X is extremely well thought out, well designed and easily capable of providing everything we need.
OK... so then design a better font handling system for X and get it incorporated for X11R7!
Don't throw the baby out with the bath water!
Why oh why oh why do so many people harp on here on slashdot that X is 'bad'? Do you even understand the issues? Have you even ever tried comparing X with other windowing systems? Do you have any idea of the design goals of X?
In short, do the people who post "X sucks let get rid of it!" to threads like this have ANY feckin' clue?
"It's slow - lets get rid of it!!!":
Is it really slow? Seems fast enough to me, and I started out with X11R6 on Sparcstation 1's. Perhaps you are confusing X with XFree86?
Also, most other windowing systems have a huge advantage over X, ie they are called as library or system functions, whereas X was designed as a PROTOCOL for network transparency. This has an impact on speed but only slight, and if the X client and server are running on the same host there is no reason why they can't communicate via shared memory or some other X extension (see below). However X has something that these procedure call window systems don't: SEAMLESS network transparency. If I show you my desktop you have absolutely no way to tell which windows are running locally and which are running on various other machines round here.
"It's bloated! lets get rid of it!":
What is bloated exactly? X the protocol is a very lean protocol (though very chatty), designed with extensibility and low-latency connections in mind. ie if you can't do it with X, then go write an EXTENSION. Implementations are a different story, but again X != XFree86. (though XF4 is a different story - leaner and faster).
If the implementation you use is bloated go use a different one. Have a look at handhelds.org they're working on a small footprint X server for handhelds.
"Xlib/Xt suck!! let's get rid of X!":
Then don't use Xlib or Xt! Use Qt or GTK+.
"X sucks for fonts. let's get rid of it!":
Firstly, I bet you havn't read the X-Font-Deuglification HOWTO. Go to linuxdoc.org/HOWTO and read it and find out how to make all those sites like microsoft.com, dabs.com, etc, look right under netscape. Don't blame X cause it wasn't setup right! Blame your Vendor.
Secondly, X apparently won't handle anti-aliasing of fonts as it stands now. ("So let's get rid of it!"). HOWEVER do you know why anti-aliasing of fonts was invented? Cause in the mists of time, a lot of computers had terrible resolution screens. Anti-aliasing is a HACK to make fonts look better, nowadays we nearly all have at least 100dpi displays so you are better off setting X up CORRECTLY and getting clear fonts without anti-aliasing.
Thirdly, if there truly is a problem with font handling in X, well then let's do something about this small problem. Either implement an extension (Display Postscript springs to mind - most commercial Unices have this), or else fix X if needs be so that X11R7 has even better font handling.
In Summary:
X is one of the most amazing software concepts ever! It's like Unix, a timeless classic.
- If it can't do something, extend it!
- If it has a limitation, then get it fixed for the next major release of the X protocol!
but please stop the silly misinformed whinging and whineing.
considering the whole point of MySQL is to sacrifice the heavier features of SQL and 'Enterprise' RDBM's in the quest for speed, it'd be amazing if it wasn't faster than Oracle.
that would be the SBS (Special Boat Squadron) counterparts of the SAS.
What would you say makes a cluster a /Beowulf cluster/, as opposed to just a bunch of computers running linux linked by ethernet? What is it that differentiates the Beowulf cluster from the rest?
"configured at boot time" == kernel relinked at boot time == just like IRIX, Tru64[1], Solaris, UnixWare...
Get over it.. just about every Unix has to recompile the kernel for hardware/kernel config changes, just like linux.
1. Yes, there are other DNS servers, but BIND must surely be the most widely used on the 'net.
/immediately/ fetch the updated zone when it recieves the notify from the master, irregardless of whether any client asked for a record or not, and irregardless of whether it still has records cached that havn't expired yet.
2. I am trying to correct your mistaken belief that DNS servers don't push zone changes.
A BIND 8 slave will
Also, DNS NOTIFY is part of the DNS spec, so other servers are free to implement it.
"If a change is made, and *your* server has cached records, it won't know about the changes until the records expire"
BIND 8 has a notify mechanism whereby the master informs the other listed NS's if a zone changes.
edit the serial number on a zone and do ndc reload zone. then watch the logs as your server notifies the slaves.. then seconds later watch as named reports loads of zone transfers..
it was never ever known as Ultrix.
Also the marketing name has changed a couple of times (OSF/1 -> Digital Unix -> Tru64) But it's *real* name (ie uname) is and always has been OSF/1.
the last time i recompiled my irix kernel, must have been a couple of weeks when i re-installed a patch set from SGI.
When i rebooted it automatically relinked the kernel...
Digital Unix does the same.
Unixware does the same.
OpenServer does the same.
Hell, i can't think of any Unix where you *don't* have to recompile the kernel.
VMS is also used heavily by Intel to run their fabs.... all the intel fabs have Compaq/DEC technicians to look after the computers.
goddammit... it's *Tru*64...
SGI scsi host adapter has a scsi ID of 0, so make sure the hard disk is jumpered for ID 1.
Kan iemand dit alsjeblieft een +5 score geven. Eerste post met wat echte nieuws op Slashdot van daag!
i hate april 1.
Comparing MS qualifications to commercial pilots qualifications is wrong..
/don't/ get your qualification - you need to go get some real experience first. (it's probationary).
Firstly a commercial pilot needs a generic licence, an ATPL, which needs a lot of training, at the end of which you
As for individual aeroplanes, well there's no question of a type rating for a 737 being valid for a 757 - type ratings aren't even valid across different versions of the same plane sometimes. That'd be ludicrous. And type ratings differ from MS quals enormously in that they are regulated, eg by the FAA in the states, CAA in the UK, DoT in Ireland. The type rating has nothing to do with the vendor of the plane. (they might have had input into the requirements for the type-rating.) Also, once you have a type rating, you can stay current by getting checked out every 6 months by an instructor with the appropriate instructors type rating, and you can stay current on as many different type-ratings as you want, if you can find the time on the planes and an intructor for it.
So comparing a regulated, safety orientated, non-vendor locked, rigorous licencing scheme to a proprietary, vendor-locked, marketing orientated certification programme is mad.
(unless you want to argue that computer training should be regulated and licenced?)
oh god.. you havn't a clue have you?
the point is that this gives you complete remote access to your machine.. you have a rack of servers, you put a terminal server in and the wire all the machines into it, then you can remote boot your pc servers by telneting or dialling into the term server.
CPQ has had this for a while now (Insight something). It used to be a card (with a 386 on it), but now it's integrated in most new proliant servers, you just enable it in Compaq's config utility.
Aarrrggghhh...
It was not MS that gave up - it was Compaq!!!! Compaq decided to drop support for NT on Alpha!!
Who do you think had to maintain Alpha/NT? Clue: Not MS. Yes, DEC/Compaq had to pay for a complete NT software development dept., because DEC/Compaq had to do the maintenance. (same thing when NT used to run on PPC - IBM had to maintain it, until they realised it didn't sell).
Then some bright spark looked at the figures and realised that nobody was buying NT on Alpha. It's best marketshare was on workstations - ~15%!! On servers it was even worse - because people who tend to buy nice hardware like Alpha also tend to buy nice OS's like OpenVMS or Unix. People were not spending money on Alpha/NT.
They put 2 and 2 together and realised that paying for NT/Alpha was costing more than the revenues generated by Alpha/NT sales. And that's why it was scrapped. The biggest money maker on Alpha is Unix, closely followed by VMS.
Also, look how hard compaq is pushing Linux on Alpha. This is for the same reason as why NT was dropped - money. Linux sells a lot of Alpha's.. esp in the lower end, eg Linux marketshare on DS10's is about 40% or higher... it also does well on clusters. And Compaq is pushing linux/alpha clusters really hard.
(my mouse mat is a picture of tux on a fat motorcycle with the Compaq Alpha logo, and a banner saying "Linux SCREEEEAMMMS on Compaq Alpha".. this is an official compaq mousemat)
:)
in fact this Alpha cluster will most likely run linux..
While you are right that narrow/wide has 8/16 target ID's, that does not neccessarily mean you can plug 7/15 devices onto a SCSI bus.
Eg, Ultra will not really tolerate more than 4 devices on a bus. It's possible to have 5 or 6 Ultra devices on the same bus, but you are likely to have problems.
ermmm.. actually a lot of Win software did use to have the "Regents of California" coyright statement. Eg ftp on older WinXX installs would print it out when you started it. (code had to actually print it out to the user - nothing to do with code comments)
..." in WinXX today. But still that code is BSD based - eg the WinXX tcp/ip stack was developed from BSD. A lot of the utilities (ftp, traceroute, etc.) are BSD based.. etc..
However the "must display copyright" clause was removed from the BSD licence about a year or 3 ago. I believe it was RMS that persuaded them. Hence the reason why you can't find "Regents
OSF1 is then the name of the kernel.[1]
Tru64 is the marketing name of the system.
similar to:
uname on Sun always gives SunOS x.y(kernel)
Yet SunOS 5+ is known as "Solaris" -> system/marketing.
[1]. Open Software Foundation.
ironically enough x86 now supports more memory than Alpha, which is limited to to 2GB on most machines because of PCI.. :(
hope someone fixes this soon.
what about SCSI DVD drives? Do they exist? And if so, do they work with linux, and which would you recommend?