If I remember what I've read before correctly, POWER is little-endian. When Apple/IBM/Motorola started working on the PowerPC, one of their goals was to run AIX and MacOS (though not simultaneously). And, as we know, 680x0 processors were big-endian. So, the PowerPC was given an endianness switch, and the firmware was tasked with flipping it into the required position during boot.
There's more detail about the PowerPC's heritage (including its relation to Motorola's 88000 processor) in this Wikipedia page.
AIX/i386 gets mentioned a few times in the OS/2 Warp manuals, in the chapters that deal with disk partitioning and the IBM Boot Manager. Other than that, it's pretty much forgotten.
I wouldn't worry too much, really. After all, this is only the first beta, and will hopefully have some time to switch to GCC 3.2. Such a change should be pretty smooth, given that the only item in the list of changes on the page you mentioned is:
The C++ ABI now conforms to the V3 multi-vendor standard.
I sincerely hope that GCC's C++ ABI remains stable from here on. It has been, IIRC, the single biggest source of incompatible GCC version issues.
Thanks for the info. Looking at the documentation on its website, it seems that Aegis is also capable of using Make and RCS instead of Cook and FHist, which would probably help those moving from other CM's. I've never used Cook, but I think I'll give it a try and see how it fares.
Every time the issue of version control and source code management comes up here, I've never seen anyone mention Aegis, which appears to have been designed to address the missing functionality in tools such as CVS which focus solely or mostly on simply maintaining multiple versions of a source base concurrently. Here's an excerpt from the CVS comparison in the CVS Transition Guide:
1.5.1. Why should I change from CVS to Aegis?
Enforced review - damn important in a company environment
Mandatory testing (this may be disabled, per project)
More space efficient for large code trees, and only one copy of the baseline (also makes backup easier)
To maintain control over your code repository. The baseline can't even be written to by developers, so the audit trail is more secure.
Support for change sets. My main complaint with CVS is that you are unable to associate modified files into a change so once the files are committed to the CVS repository, there is no easy way to back it out or work out which other files were changed as part of a logical set.
Separation of the roles of developer, reviewer and integrator. At the moment, typical distributed CVS development happens with people checking in stuff as they develop it with very little integration testing as they go along. It's pretty much up to people "in the know" to manually go through changed files and
check to see if something has been broken by a developer. It gets even tricker when there are particular assumptions made that aren't written down.
Automated testing support.
The software seems to be pretty mature (currently at version 4.5, first released in 1991). Has anyone here used it?
Given that we're discussing this within Slashdot and its context, I suggest that we rename it to Minimal Extensible Exchange Protocol Toolkit. Additionally, this protocol should perform every action within a single, long transaction encapsulating multiple exchanges, e.g.:
It's the whitelist_from option; it takes a fileglob-style argument to specify a sender whose e-mail will not be checked. E.g., "whitelist_from *@slashdot.org" would whitelist e-mail from Slashdot. The default configuration includes a number of whitelisted addresses by default. The corresponding blacklist_from option is there too, along with whitelist_to, more_spam_to, and all_spam_to.
I once went through the hassle of setting up my US keyboard in XFree 3.x to emulate Windows' US-International layout (I had become very accustomed to it). One thing I quickly learned is that using Compose is uncomfortably clumsy, and usually didn't work the way I expected it to. That's when I found about XKeycaps, a little X program written using libXaw that allows the user to produce an xmodmap file visually. I eventually did something like this:
Assigned Mode_shift to RightAlt (AltGr, if your keyboard has that);
Changed the apostrophe to dead_acute, double quote to dead_diaeresis, backtick to dead_grave, asciitilde to dead_tilde, and asciicircum to dead_circumflex;
Assigned alternate graphs to various keys, so that they'd work the same way they'd do under Windows when Mode_shift is pressed.
IIRC, XF4 comes with a "us_intl" layout that is similar ("XkbLayout('us_intl')" in XFree86config, I think), but too many things were different from what I expected that I still kept using my old xmodmap file. It does provide for a good starting point, however; you won't have to do as much with xmodmap as a result.
Here in Canada, it's pretty easy" 5's are blue, 10's are purple, 20's are green and 50's are red.
I always thought of it as "5's have '5' printed on them, 10's have a '10'," etc. And coins are the same size and shape as US coins, except for the toonie. And, yes, I'm a 'merkin.
Not necessarily. Who's saying that they won't be producing these discs inside CompactFlash cards? This might actually help pump up the storage capacity of microdrives.
A fan without ball bearings in it, too, so if the bushing breaks, you're left with a very annoyingly noisy machine. It'd otherwise still be very quiet, since the fan usually isn't so loud.
Slashdot Mirror
But we'll have to wait 93 years for the release of KDE '95.
But our standards are good! We have so many to choose from!
Now there's a PDA that Steve Irwin would be happy to use.
If I remember what I've read before correctly, POWER is little-endian. When Apple/IBM/Motorola started working on the PowerPC, one of their goals was to run AIX and MacOS (though not simultaneously). And, as we know, 680x0 processors were big-endian. So, the PowerPC was given an endianness switch, and the firmware was tasked with flipping it into the required position during boot.
There's more detail about the PowerPC's heritage (including its relation to Motorola's 88000 processor) in this Wikipedia page.
Thank God, I am ambidexterous.
AIX/i386 gets mentioned a few times in the OS/2 Warp manuals, in the chapters that deal with disk partitioning and the IBM Boot Manager. Other than that, it's pretty much forgotten.
I wouldn't worry too much, really. After all, this is only the first beta, and will hopefully have some time to switch to GCC 3.2. Such a change should be pretty smooth, given that the only item in the list of changes on the page you mentioned is:
I sincerely hope that GCC's C++ ABI remains stable from here on. It has been, IIRC, the single biggest source of incompatible GCC version issues.
Thanks for the info. Looking at the documentation on its website, it seems that Aegis is also capable of using Make and RCS instead of Cook and FHist, which would probably help those moving from other CM's. I've never used Cook, but I think I'll give it a try and see how it fares.
Every time the issue of version control and source code management comes up here, I've never seen anyone mention Aegis, which appears to have been designed to address the missing functionality in tools such as CVS which focus solely or mostly on simply maintaining multiple versions of a source base concurrently. Here's an excerpt from the CVS comparison in the CVS Transition Guide:
1.5.1. Why should I change from CVS to Aegis?
The software seems to be pretty mature (currently at version 4.5, first released in 1991). Has anyone here used it?
Given that we're discussing this within Slashdot and its context, I suggest that we rename it to Minimal Extensible Exchange Protocol Toolkit. Additionally, this protocol should perform every action within a single, long transaction encapsulating multiple exchanges, e.g.:
MEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEPT!
This bit really stood up, IMO:
And it could not be explained any more simply than that.
They should go all the way and integrate either one of these into the packaging:
Suddenly, Athlons seem mighty cool (literally).
Is your network of monkeys RFC-2795-compliant?
It's the whitelist_from option; it takes a fileglob-style argument to specify a sender whose e-mail will not be checked. E.g., "whitelist_from *@slashdot.org" would whitelist e-mail from Slashdot. The default configuration includes a number of whitelisted addresses by default. The corresponding blacklist_from option is there too, along with whitelist_to, more_spam_to, and all_spam_to.
At this point, I'm confident enough to guess that God's account is now 'entwhistle' instead of 'pete'.
Don't shut your mouths up! You'll be in violation of yet another stupid copyright!
I once went through the hassle of setting up my US keyboard in XFree 3.x to emulate Windows' US-International layout (I had become very accustomed to it). One thing I quickly learned is that using Compose is uncomfortably clumsy, and usually didn't work the way I expected it to. That's when I found about XKeycaps, a little X program written using libXaw that allows the user to produce an xmodmap file visually. I eventually did something like this:
IIRC, XF4 comes with a "us_intl" layout that is similar ("XkbLayout('us_intl')" in XFree86config, I think), but too many things were different from what I expected that I still kept using my old xmodmap file. It does provide for a good starting point, however; you won't have to do as much with xmodmap as a result.
Sure, but does Teoma have doodles? And if it does, what'd they call them? Toodles?
It looks like the discography from Brazilian progressive rock band Angra. At least nine of those items are the titles to some of their songs.
I hate to do this, but I feel obligated to correct you. The actual name (plus slogan) is:
It's all right here.
Eh, I never saw it that way.
I always thought of it as "5's have '5' printed on them, 10's have a '10'," etc. And coins are the same size and shape as US coins, except for the toonie. And, yes, I'm a 'merkin.
Not necessarily. Who's saying that they won't be producing these discs inside CompactFlash cards? This might actually help pump up the storage capacity of microdrives.
"Opteron" is the name of the SMP-capable Hammer -- the non-SMP version will carry the old name, "Athlon". Look here for more.
Personally, I very much prefer calling it "Hammer". It's much easier to pronounce, for one.
Help, Yoda can:
If at a map of the United States a dart you throw, access broadband even if they wanted to much of the nation can't.
Better now?
A fan without ball bearings in it, too, so if the bushing breaks, you're left with a very annoyingly noisy machine. It'd otherwise still be very quiet, since the fan usually isn't so loud.