Re:Still lives within the EV6 AMD Athlon...
on
End In Sight For Alpha
·
· Score: 5, Informative
The speed increases on the p4 is due to the use of a 22 stage pipeline. The Athlon and Alpha do not have nearly that long a pipeline and as such do not scale in Mhz as easily, but they get more work done per clock, hence why a slower Athlon is on par with a p4.
>Now that we're done with that point, let's move on to the next point, about code-morphing and talking about changing the chip "to a PowerPC, MIPS, or SPARC-compatible chip in seconds" For one thing, assuming you would want todo this in a laptop, can you even imagine the problems with hardware? Can you point me to a motherboard, video card, sound card, or heck, even recent ram manufacturer that makes one component that works on x85,PPC,SPARC and MIPS platforms?
Actually, there wouldn't be any issues with hardware, except for driver support and maybe the video card. Remember, transmeta's chip will use a transmeta motherboard. Support a transmeta motherboard, you're done. As for sound cards, they're PCI devices, they could care less about what platform they are on. I can use the same sound card on Alpha/x86/Sun/SGI whatever. Of course, driver support is a new issue. Video card typically have a small amount of BIOS code on them to allow for video output before the OS loads. That is the only thing that would pose a problem. However, since the Cruse could switch from x86 (which most video BIOSes are written for) to say SPARC right after the video initialized, it wouldn't pose too much of a problem. Remember, this is just changing what opcodes the processor interprets, not anything hardware wise.
But, at least on a UNIX system, you can take the name of a process in ps -ef and do "man processname" and usually get some info telling you what it is.
At least with Mathmatica 4.0, the linux install is simply a shell script. I haven't had any problems with it on a 2.4.x kernel. You really just need a relatively up to date distro and it'll work fine.
but I recently had to get Solaris interacting with AD. After digging around and finding no real definitive documentation, I found a set of PAM and nsswitch modules from PADL that provide LDAP support for both setups.
After getting these to compile properly on Solaris (which was it's own nightmare, though they work out of the box for Linux), I had to install the AD4UNIX package. This is a program/plugin/schema update maintained at this site that adds the MS Servies for UNIX version 2 schema to the AD. This gives you places to store uids, gids, home directory, etc. It also gives a nice plugin for the AD user manager to let you set that data.
Finally, you edit a few config files (non-trivial, but possible) and suddenly you have AD users appearing in your passwd entries, and they can login with anything that uses PAM.
Like I said, i don't know how much that would apply to OS X (I haven't had a chance to play with it yet), but if you have PAM and NSS, it does work.
Also, I'm gonna put my notes online once i clean them up so that no other poor sysadmin has to dig for it.
Actually, AD is based entirely on Kerberos and LDAP. It's very easy to interoperate with. In fact you can even have sendmail and postfix automatically setup mail aliases from AD info. It's really neat but not well documented on how to do it. I recently got Solaris talking with AD for authentication. I can now easily pull all sorts of info from AD.
You obviously didn't bother to read anything at the link provided. It offers a web interface, POP3 and IMAP (hence server-side storage), uses standard mailstores and OpenLDAP for the calandering and such. Recovery of mbox mailboxes is fairly trivial, however, I know nothing of recovering OpenLDAP (it seems to be Berkley DB so that should be possible). Accessing ex-employees info is simple, just reassign access to the OpenLDAP data and append the mbox to someone else. Heck, it's probably even an automated option in the web interface. As for mailbox recovery, if you delete a mbox, it's gone. That's why you have tape. I personally think it's stupid for Exchange to keep the data around after you delete someone. Talk about a long-term waste of space.
And just to be annoying. If you had read the article you would have found out that this was not a configuration issue or even an issue with the binary, but a trojan horse implanted in the configure script.
Well, the pre-install is to download the ISO and burn it to a CD. Simply boot off the CD and follow the directions to actually boot (you can also use it as a rescue disk and we included memtest86 as well).
After you boot the CD, it'll present you with dialog based menus. Simply follow the prompts and you can partition and format your drives (optional) and you can transfer the Lunar install to the harddrive (the CD is actually the base install plus an extra script). After the install is transfered, you can configure your kernel and it is compiled and installed. Finally, configure your network interfaces and reboot.
Post-install is the brunt of the work. You have a fully usable system at this point, but only with the bare minimum of applications. You have a few text editors, the basic system utilities, the networking tools and startup scripts and a few various other packages.
If you plan on using a DHCP network connection, you will need to first install the dhcp client you chose during the network configuration. Typically this is dhcpcd. All you type is 'lin dhcpcd'. The source for dhcpcd, dhclient, the kernel, and pcmcia-cs are included in the install. This allows nearly anyone to get online to download the other sources they need (including wireless cards). After your dhcp client is installed, run/etc/init.d/network restart to enable the interface.
Otherwise, simply use the command 'lin' and a package name to install a package. If you want to know what packages are available, 'lvu section' lists the sections of the moonbase (this software database), and 'lvu section (section name)' lists the packages in that section. lin will prompt you for any optional dependencies and/or configuration options you want to use for the package and it's selected dependencies. After you answer all the questions, lin will download the source, compile it, create a log of the compile messages, create a log of the installed files, and finally create a archive of the binary files installed. Many of the things that happen during a 'lin' can be adjusted through the use of the 'lunar' program.
'lunar' provides a dialog based interface to configure the behaviour of the lunar packaging tools.
Also, if you decide you do not want a package installed anymore, simply type 'lrm (package)' and it will be removed.
Funny you mention that comment, I wrote it. We offer an easier installation than Gentoo. Rather than providing users the choice of how to begin the installation (tough for a new linux user), we simply say, use the CD. Is that necessarily better? For a new user yes. However, past the installation, users are confronted with configuration of things such as X without much help. Now, there are a few scripts provided to ease the setup of network interfaces (lnet) and to setup your mouse for GPM (lmouse), but most of the configuration is left up to you.
I personally see the future of Lunar linux going towards an easy to install, easy to configure source distribution (the built from source at install kind). I do not know how all the developers view the future of Lunar however.
But, as far as getting a base system up and running, Lunar is much easier for newer linux users than Gentoo.
so it did a slow death spiral until finally being bought up by Intel last year.
Well, Intel bought some of the patents, but the rights to actually produce a functioning Alpha processor are still held by Compaq and API. Actually, Alphas are still being manufactured until 2005 with the ev78(?) being the last in the line.
Re:Windows XP reason we need more than 4GB?
on
AMD's 64-Bit Chip
·
· Score: 1
What are you using? MS SQL? I've seen Oracle do more on less hardware than that.
Re:Why doesn't the Alpha matter anymore?
on
AMD's 64-Bit Chip
·
· Score: 1
Well, DEC's biggest problem was selling the Alpha. They may have had a superior product, but not a clue as to how to market or support it.
As for the non-relevance, the Athlon takes quite a bit of the technilogical experience from the Alphas. The Athlon uses many of the ideas and even the processor interface (albeit in a modified form) of the Alphas. Many of the engineers that built the Alpha series went on to work with either Intel or AMD.
Like I said, marketing wasn't their thing. It's why the Alpha never suceeded in anything more than a niche market. If you had a purpose for an Alpha (scientific computation or really big database or anything that required lots of floating point), it was the best option, but otherwise, no one could really find a reason for one.
I own a AlphaStation 600 and I can attest that they did many things right overall. Now if I could just get another free Alpha, hopefully a newer one.
You obviously have no idea as to how much intra-network file swapping is done at Case. When my brother attended, it was difficult to hit 100Mbps because the line to the dorm couldn't handle everyone pulling that fast.
It's not so much Internet traffic at Case that's the problem, but rather intra-dorm traffic.
I don't know about everywhere, but the college I attend has the computer science program as part of the engineering college. We both get Bachelors of Science as well.
So, how is being a "real engineer" different from a "science person"?
Last time I checked, the only difference between computer science and computer engineering was that the engineers are more geared towards building processors and integrated circuits whereas scientists are preped for software design.
And BTW, software DESIGN is taught in college as part of the CS program. The idea that most programs are simply written by a single programmer who sits down and start spewing out code has been wrong for many years. But even the best designs still have flaws.
I had one of these as well. The best game for it was "Pick Axe Pete". Another one of those great games that you could never beat because it never ended.
Sadly, my brother and I sold the Odyssey II and all the games (25 or so) at a garage sale. I'll have to go buy one again. There are a few places that have them for relatively cheap and a decent selection of games.
I happened to view this when they aired at 7pm. The consoles are pretty much matched up to the front of the case. The Xbox and the Atari are the only that have the connectors in the front with a jumper to the unit. Anyway, if you look at the front, the bottom left corner is the PS2, the 5.25" Drive bays on top are the Gamecube, the Xbox and Atari controllers are in the front below the switches for power and reset and the nintendo is off to the top right. It was pretty impressive.
Slashdot Mirror
The speed increases on the p4 is due to the use of a 22 stage pipeline. The Athlon and Alpha do not have nearly that long a pipeline and as such do not scale in Mhz as easily, but they get more work done per clock, hence why a slower Athlon is on par with a p4.
Who the heck thought modding this flamebait informative was a good idea?
>Now that we're done with that point, let's move on to the next point, about code-morphing and talking about changing the chip "to a PowerPC, MIPS, or SPARC-compatible chip in seconds" For one thing, assuming you would want todo this in a laptop, can you even imagine the problems with hardware? Can you point me to a motherboard, video card, sound card, or heck, even recent ram manufacturer that makes one component that works on x85,PPC,SPARC and MIPS platforms?
Actually, there wouldn't be any issues with hardware, except for driver support and maybe the video card. Remember, transmeta's chip will use a transmeta motherboard. Support a transmeta motherboard, you're done. As for sound cards, they're PCI devices, they could care less about what platform they are on. I can use the same sound card on Alpha/x86/Sun/SGI whatever. Of course, driver support is a new issue. Video card typically have a small amount of BIOS code on them to allow for video output before the OS loads. That is the only thing that would pose a problem. However, since the Cruse could switch from x86 (which most video BIOSes are written for) to say SPARC right after the video initialized, it wouldn't pose too much of a problem. Remember, this is just changing what opcodes the processor interprets, not anything hardware wise.
But, at least on a UNIX system, you can take the name of a process in ps -ef and do "man processname" and usually get some info telling you what it is.
At least with Mathmatica 4.0, the linux install is simply a shell script. I haven't had any problems with it on a 2.4.x kernel. You really just need a relatively up to date distro and it'll work fine.
mplayer starts CLI, gmplayer starts gui. It's been that way for a while.
but I recently had to get Solaris interacting with AD. After digging around and finding no real definitive documentation, I found a set of PAM and nsswitch modules from PADL that provide LDAP support for both setups.
After getting these to compile properly on Solaris (which was it's own nightmare, though they work out of the box for Linux), I had to install the AD4UNIX package. This is a program/plugin/schema update maintained at this site that adds the MS Servies for UNIX version 2 schema to the AD. This gives you places to store uids, gids, home directory, etc. It also gives a nice plugin for the AD user manager to let you set that data.
Finally, you edit a few config files (non-trivial, but possible) and suddenly you have AD users appearing in your passwd entries, and they can login with anything that uses PAM.
Like I said, i don't know how much that would apply to OS X (I haven't had a chance to play with it yet), but if you have PAM and NSS, it does work.
Also, I'm gonna put my notes online once i clean them up so that no other poor sysadmin has to dig for it.
I hate to burst your bubble, but talk existed well before ICQ. It existed way back when UNIX was new.
Actually, AD is based entirely on Kerberos and LDAP. It's very easy to interoperate with. In fact you can even have sendmail and postfix automatically setup mail aliases from AD info. It's really neat but not well documented on how to do it. I recently got Solaris talking with AD for authentication. I can now easily pull all sorts of info from AD.
You obviously didn't bother to read anything at the link provided. It offers a web interface, POP3 and IMAP (hence server-side storage), uses standard mailstores and OpenLDAP for the calandering and such. Recovery of mbox mailboxes is fairly trivial, however, I know nothing of recovering OpenLDAP (it seems to be Berkley DB so that should be possible). Accessing ex-employees info is simple, just reassign access to the OpenLDAP data and append the mbox to someone else. Heck, it's probably even an automated option in the web interface. As for mailbox recovery, if you delete a mbox, it's gone. That's why you have tape. I personally think it's stupid for Exchange to keep the data around after you delete someone. Talk about a long-term waste of space.
And just to be annoying. If you had read the article you would have found out that this was not a configuration issue or even an issue with the binary, but a trojan horse implanted in the configure script.
However, I much prefer postfix anyway.
Well, the pre-install is to download the ISO and burn it to a CD. Simply boot off the CD and follow the directions to actually boot (you can also use it as a rescue disk and we included memtest86 as well).
/etc/init.d/network restart to enable the interface.
After you boot the CD, it'll present you with dialog based menus. Simply follow the prompts and you can partition and format your drives (optional) and you can transfer the Lunar install to the harddrive (the CD is actually the base install plus an extra script). After the install is transfered, you can configure your kernel and it is compiled and installed. Finally, configure your network interfaces and reboot.
Post-install is the brunt of the work. You have a fully usable system at this point, but only with the bare minimum of applications. You have a few text editors, the basic system utilities, the networking tools and startup scripts and a few various other packages.
If you plan on using a DHCP network connection, you will need to first install the dhcp client you chose during the network configuration. Typically this is dhcpcd. All you type is 'lin dhcpcd'. The source for dhcpcd, dhclient, the kernel, and pcmcia-cs are included in the install. This allows nearly anyone to get online to download the other sources they need (including wireless cards). After your dhcp client is installed, run
Otherwise, simply use the command 'lin' and a package name to install a package. If you want to know what packages are available, 'lvu section' lists the sections of the moonbase (this software database), and 'lvu section (section name)' lists the packages in that section. lin will prompt you for any optional dependencies and/or configuration options you want to use for the package and it's selected dependencies. After you answer all the questions, lin will download the source, compile it, create a log of the compile messages, create a log of the installed files, and finally create a archive of the binary files installed. Many of the things that happen during a 'lin' can be adjusted through the use of the 'lunar' program.
'lunar' provides a dialog based interface to configure the behaviour of the lunar packaging tools.
Also, if you decide you do not want a package installed anymore, simply type 'lrm (package)' and it will be removed.
That is the pre/during/post-install experience.
Funny you mention that comment, I wrote it. We offer an easier installation than Gentoo. Rather than providing users the choice of how to begin the installation (tough for a new linux user), we simply say, use the CD. Is that necessarily better? For a new user yes. However, past the installation, users are confronted with configuration of things such as X without much help. Now, there are a few scripts provided to ease the setup of network interfaces (lnet) and to setup your mouse for GPM (lmouse), but most of the configuration is left up to you.
I personally see the future of Lunar linux going towards an easy to install, easy to configure source distribution (the built from source at install kind). I do not know how all the developers view the future of Lunar however.
But, as far as getting a base system up and running, Lunar is much easier for newer linux users than Gentoo.
but remember, WINE Is Not an Emulator.
It's a wrapper that maps windows library calls to UNIX system calls.
so it did a slow death spiral until finally being bought up by Intel last year.
Well, Intel bought some of the patents, but the rights to actually produce a functioning Alpha processor are still held by Compaq and API. Actually, Alphas are still being manufactured until 2005 with the ev78(?) being the last in the line.
What are you using? MS SQL? I've seen Oracle do more on less hardware than that.
Well, DEC's biggest problem was selling the Alpha. They may have had a superior product, but not a clue as to how to market or support it.
As for the non-relevance, the Athlon takes quite a bit of the technilogical experience from the Alphas. The Athlon uses many of the ideas and even the processor interface (albeit in a modified form) of the Alphas. Many of the engineers that built the Alpha series went on to work with either Intel or AMD.
Like I said, marketing wasn't their thing. It's why the Alpha never suceeded in anything more than a niche market. If you had a purpose for an Alpha (scientific computation or really big database or anything that required lots of floating point), it was the best option, but otherwise, no one could really find a reason for one.
I own a AlphaStation 600 and I can attest that they did many things right overall. Now if I could just get another free Alpha, hopefully a newer one.
My brother actually got to lease a fiber card for his box a few years ago when he was attending case.
You obviously have no idea as to how much intra-network file swapping is done at Case. When my brother attended, it was difficult to hit 100Mbps because the line to the dorm couldn't handle everyone pulling that fast.
It's not so much Internet traffic at Case that's the problem, but rather intra-dorm traffic.
I don't know about everywhere, but the college I attend has the computer science program as part of the engineering college. We both get Bachelors of Science as well.
So, how is being a "real engineer" different from a "science person"?
Last time I checked, the only difference between computer science and computer engineering was that the engineers are more geared towards building processors and integrated circuits whereas scientists are preped for software design.
And BTW, software DESIGN is taught in college as part of the CS program. The idea that most programs are simply written by a single programmer who sits down and start spewing out code has been wrong for many years. But even the best designs still have flaws.
I had one of these as well. The best game for it was "Pick Axe Pete". Another one of those great games that you could never beat because it never ended.
Sadly, my brother and I sold the Odyssey II and all the games (25 or so) at a garage sale. I'll have to go buy one again. There are a few places that have them for relatively cheap and a decent selection of games.
Anyway, back to work.
I was wondering how long it would take someone to make that reference.
But really, how many ELF binaries are in your ~?
This reminds me of 386DX. It's just about as bad, but he pulls it off on a 386 with 4MB of RAM.
I happened to view this when they aired at 7pm. The consoles are pretty much matched up to the front of the case. The Xbox and the Atari are the only that have the connectors in the front with a jumper to the unit. Anyway, if you look at the front, the bottom left corner is the PS2, the 5.25" Drive bays on top are the Gamecube, the Xbox and Atari controllers are in the front below the switches for power and reset and the nintendo is off to the top right. It was pretty impressive.