Unless the OOo project moves to a file format that would support a Reveal Codes feature, this would be impossible. Without Reveal Codes, a WP user will not switch to another wordprocessor.
Sony's PlayStation 3 will use 3 CPUs based on the POWER/PowerPC architecture. Not PowerPC CPUs directly, but similar.
Nintendo has also made a few public nods toward IBM's POWER/PowerPC for its next-gen console. However, since there are no real, public plans for their next-gen console, this isn't really worth noting.
PowerPC is also used quite often in the embedded world due to its low heat output and low power requirements.
This is exactly the path that Intel is taking. The next generation of CPUs will be based on the Pentium-M architecture (which is nothing more than a Pentium-!!! with a few P4 technology bits thrown in). The CPUs run slower (1.7 GHz currently) and a hell of a lot cooler, but perform just as well as a P4 1000 MHz faster.
There have been at least 2 stories about this on Slashdot and Ars Technica. Check'm out.
but make your own packages. This way, you get the ease of install / uninstall / upgrade / query that the package manager gives you, but you get the full optimisation and feature control that you get with installing from source.
Or, switch to an OS that uses the same methods for building packages as installing from source (like the ports trees in OpenBSD and FreeBSD, or the pkgsrc system from NetBSD).
Either use the package manager for everything, or only install from source. If you try to do both, you will run into all kinds of problems. We have 30+ RedHat servers running with a mix of RPMs and source installs, and it's a royal mess to install anything. Try to use the RPM and it complains that you don't have libX version Y... but you do because it was installed via source last week. It's horrible, and I've been trying to fix it for the past couple months (RPM spec files suck).
True, they haven't done that yet. Hopefully, maybe, under the next blue moon, they'll do something along the lines of the Viewer apps for Unix systems.
This is why I keep a lone Windows 98 system at home... just in case.
What's even funnier about the whole "UI is different, will require retraining" is that the Office UI has *never* been consistent from one version to the next.:) Pretty hard to claim the UI as good thing in Office, when they keep changing it (and not always in good ways).
If the UI is so good, why change it so drastically with each new version of Office??
Haven't tried it yet, but The Kompany just released their GUI/RAD database tool as open source. Don't recall the name of it, but it's listed on their products page, and slashdot ran a story about it a few months back.
You need to separate "reading other people's docs" from "creating my own docs".
Use whatever office suite you want to create your own documents. Use OpenOffice.org, StarOffice, KOffice, GNOME Office, Wordperfect Office, SmartSuite. Hell, use notepad if you really want.
For viewing other people's documents (including presentations) just grab the viewer apps for those formats. Microsoft provides free viewers for all office formats since 97 in their Word Viewer, Excel Viewer, and PowerPoint Viewer software (free downloads from the Office site). There's also the Inso Corporation viewers and QuickView which supports just about every office / image format under the sun.
Just because someone else decides they need to use Office, doesn't mean you have to.
The local ISP here does just that with their point-to-point wireless packages. You get 1.5 Mbit/s (cheapest) up to 6 Mbit/s (business) bi-directional connectivity. And they give you a Pentium 166 MHz system with 2 bootable Linux floppies preconfigured to do NAT and packet filtering. Worked like a charm for the year I used their service. They're doing great with their service, even with the non-techies. And they keep backup imags of the floppies in case the ones they give you die. It's not a perfect setup, but it works.
I think what he means is that Outlook (an MS product) is responsible for spreading more virii/worms/trojans than all the other e-mail clients combined. Hell, you group together MS Office products, and you'll probably find that they are the cause for the vast marjority of all security problems on Windows. That's the disproportionate part.
You don't see a "Eudora patch of the week" or "Another exploit found in Pegasus Mail" or "Wordperfect users are forced to upgrade, yet again, to fix a basic security flaw" headlines.
We have similar rules (dress code, no cell, no pager, etc) here (school district) as well, but the IT Department is exempted from most of them. Why? Because we need most of those things to get our job done. No sense mucking about under counters, in wiring closets, in crawlspaces, etc in nice dress pants and carrying cases around all day in dress shoes. And I couldn't live without my cell's text messaging alerts when services go down (I usually have things back up and running by the time I get the call that something isn't working).
Then again, out IT manager is tight with the superintendent and directors of education.:) Anything that makes our jobs harder to do get protested right at the top.
Make a case for why you *need* (not want) your cell phone for business purposes, during business hours. Take that to your manager and get them on board. Then take it to their manager, and so on up the ladder. Eventually, you should be able to get an exemption from the rule, either for yourself, or the entire IT dept.
The packet filtering software on Linux is horrible. The syntax is just nasty. And there are no guarantees it won't change again with the next kernel release.
Use a BSD system, with a real packet filter. FreeBSD gives you the choice of IPFW, IPF, or PF. OpenBSD gives you PF. NetBSD gives you IPF or PF. All of those have much larger / better features sets than IPChains / IPTables, and work a *lot* better in NAT/PAT/MASQ situations. These packet filters are also truly stateful (last time I checked IPTables, it wasn't truly stateful without a bunch of extra patches).
Linux makes an OK home firewall. But I wouldn't use it anywhere near a business.
We use FreeBSD 4.9 on Pentium 166 MHz systems with 128 MB RAM using IPFW to server secondary schools with just under 300 student computers. Haven't had any problems yet with network slowdowns or dropoffs or anything. These are on T1s in the remote schools, and 8 Mbit cable in town.
(I had problems keeping a similar box running Linux and IPTables working on my home wireless T1-equiv link.)
Close. The Pentium-M uses the Pentium-III core, with some P4 stuff (better branch prediction, slightly deeper pipeline, etc) tacked on top. The Pentium-M does not use the NetBurst architecture of the P4. There's a very nice, in-depth look at the Pentium-M over on Ars Techinca.
Dude, you are so far out in left field, you may as well start planting daisies.
The new license does *NOT* apply to any of the XFree86 libraries. Hence, there *ARE NO CHANGES* in the way things work, regarding linking to XFree86 libraries. IOW, NOTHING HAS CHANGED, in this regard.
The reason for the bruhaha is nothing more than laziness on the part of the various distros. They don't want to take the time to put "This project includes software from the XFree86 Project." into any of the end-user documentation. IOW, nobody wants to give credit to the XFree86 Project, yet they all want to use software from the XFree86 Project.
In the past 4 weeks, it's managed to block: 244 virus messages 416 spam messages correctly tagged 450 messages as possible spam (kill setting is low right now while I test the system).
And that's just on my 3 e-mail accounts. I haven't put this into testing inside the department yet.:)
The problem isn't that Intel is creating an AMD64-compatible chip. That's a good thing.
The problem is that Intel is not crediting AMD for all their work on the AMD64 architecture and instructions. All the Intel literature gives the impression that Intel created the whole 64-bit x86 ISA. This is just wrong, underhanded, and petty.
It was a joke. Intel released the i386 to the world when the "advanced" 16-bit DOS and 16-bit OS/2 were around. No 32-bit OS in sight. It wasn't until several years later that NT (the first truly 32-bit Windows) was released, and several more until the hybrid, consumer-level Windows 95 hit the market (OS/2 was 32-bit long before, but didn't make much of a dent).
But, their "main" reason for not releasing a 64-bit chip was because there was no 64-bit capable OS. Doesn't really follow from their past CPU releases, now does it?
This is a great little util. I really like the burn-in tests, and the fact that it can test the different RAM slots independently (on most mobos). Trying to figure out which stick of RAM is bad in a 4 GB system using memtest86 takes too long, and involves too many stops to replace the RAM chip. This way, I just let it run overnight and remove the faulty chip when it's done.
The other tests are nice, and useful as well. And having it all on a bootable floppy is nice, as you don't have to worry about having a working OS on the system.
Use it in place of your BBQ.:) Cook an entire roast pig in less than 5 minutes. Tim Allen would love this, and you'd probably get a spot on The Man Show as well.:)
The GENERIC kernelk comes with support for virtually everything, except sound. However, any device driver that is not explicitly compiled into the kernel is available as a module (including sound). So, it's just a matter of browsing through/boot/kernel/*.ko or/modules/*.ko and loading the appropriate driver.
Once you know which driver is needed, you can either edit/boot/loader.conf to have the module loaded at boot time automatically, or you can compile a custom kernel with that driver built in.
The Windows GUI shell (or window manager) is called explorer.exe. This program, and the associated libs, control the entire GUI environment.
There have been replacement shells since the release of Windows 95 and NT 4. Some are quite nice (darkstep / litestep), some are nifty (98Lite) some are just bizarre. But, there are still plenty out there to choose from.
The only interesting thing to be gleaned from the source of explorer.exe and libs would be how they get things like the RUN dialog, or system folder like My Documents to work. These are usually the bits you lose when you run a replacement shell.
Slashdot Mirror
Unless the OOo project moves to a file format that would support a Reveal Codes feature, this would be impossible. Without Reveal Codes, a WP user will not switch to another wordprocessor.
Sony's PlayStation 3 will use 3 CPUs based on the POWER/PowerPC architecture. Not PowerPC CPUs directly, but similar.
Nintendo has also made a few public nods toward IBM's POWER/PowerPC for its next-gen console. However, since there are no real, public plans for their next-gen console, this isn't really worth noting.
PowerPC is also used quite often in the embedded world due to its low heat output and low power requirements.
If PREP is based on Plato, then what's the name for the platform based on Socrates? :)
This is exactly the path that Intel is taking. The next generation of CPUs will be based on the Pentium-M architecture (which is nothing more than a Pentium-!!! with a few P4 technology bits thrown in). The CPUs run slower (1.7 GHz currently) and a hell of a lot cooler, but perform just as well as a P4 1000 MHz faster.
There have been at least 2 stories about this on Slashdot and Ars Technica. Check'm out.
but make your own packages. This way, you get the ease of install / uninstall / upgrade / query that the package manager gives you, but you get the full optimisation and feature control that you get with installing from source.
... but you do because it was installed via source last week. It's horrible, and I've been trying to fix it for the past couple months (RPM spec files suck).
Or, switch to an OS that uses the same methods for building packages as installing from source (like the ports trees in OpenBSD and FreeBSD, or the pkgsrc system from NetBSD).
Either use the package manager for everything, or only install from source. If you try to do both, you will run into all kinds of problems. We have 30+ RedHat servers running with a mix of RPMs and source installs, and it's a royal mess to install anything. Try to use the RPM and it complains that you don't have libX version Y
True, they haven't done that yet. Hopefully, maybe, under the next blue moon, they'll do something along the lines of the Viewer apps for Unix systems.
... just in case.
This is why I keep a lone Windows 98 system at home
D'oh! Sure, the one time I'm not trying to be punny, I go ahead and make a great one. :)
:D
Thanks for the reminder.
What's even funnier about the whole "UI is different, will require retraining" is that the Office UI has *never* been consistent from one version to the next. :) Pretty hard to claim the UI as good thing in Office, when they keep changing it (and not always in good ways).
If the UI is so good, why change it so drastically with each new version of Office??
Haven't tried it yet, but The Kompany just released their GUI/RAD database tool as open source. Don't recall the name of it, but it's listed on their products page, and slashdot ran a story about it a few months back.
You need to separate "reading other people's docs" from "creating my own docs".
Use whatever office suite you want to create your own documents. Use OpenOffice.org, StarOffice, KOffice, GNOME Office, Wordperfect Office, SmartSuite. Hell, use notepad if you really want.
For viewing other people's documents (including presentations) just grab the viewer apps for those formats. Microsoft provides free viewers for all office formats since 97 in their Word Viewer, Excel Viewer, and PowerPoint Viewer software (free downloads from the Office site). There's also the Inso Corporation viewers and QuickView which supports just about every office / image format under the sun.
Just because someone else decides they need to use Office, doesn't mean you have to.
The local ISP here does just that with their point-to-point wireless packages. You get 1.5 Mbit/s (cheapest) up to 6 Mbit/s (business) bi-directional connectivity. And they give you a Pentium 166 MHz system with 2 bootable Linux floppies preconfigured to do NAT and packet filtering. Worked like a charm for the year I used their service. They're doing great with their service, even with the non-techies. And they keep backup imags of the floppies in case the ones they give you die. It's not a perfect setup, but it works.
I think what he means is that Outlook (an MS product) is responsible for spreading more virii/worms/trojans than all the other e-mail clients combined. Hell, you group together MS Office products, and you'll probably find that they are the cause for the vast marjority of all security problems on Windows. That's the disproportionate part.
You don't see a "Eudora patch of the week" or "Another exploit found in Pegasus Mail" or "Wordperfect users are forced to upgrade, yet again, to fix a basic security flaw" headlines.
We have similar rules (dress code, no cell, no pager, etc) here (school district) as well, but the IT Department is exempted from most of them. Why? Because we need most of those things to get our job done. No sense mucking about under counters, in wiring closets, in crawlspaces, etc in nice dress pants and carrying cases around all day in dress shoes. And I couldn't live without my cell's text messaging alerts when services go down (I usually have things back up and running by the time I get the call that something isn't working).
:) Anything that makes our jobs harder to do get protested right at the top.
Then again, out IT manager is tight with the superintendent and directors of education.
Make a case for why you *need* (not want) your cell phone for business purposes, during business hours. Take that to your manager and get them on board. Then take it to their manager, and so on up the ladder. Eventually, you should be able to get an exemption from the rule, either for yourself, or the entire IT dept.
The packet filtering software on Linux is horrible. The syntax is just nasty. And there are no guarantees it won't change again with the next kernel release.
Use a BSD system, with a real packet filter. FreeBSD gives you the choice of IPFW, IPF, or PF. OpenBSD gives you PF. NetBSD gives you IPF or PF. All of those have much larger / better features sets than IPChains / IPTables, and work a *lot* better in NAT/PAT/MASQ situations. These packet filters are also truly stateful (last time I checked IPTables, it wasn't truly stateful without a bunch of extra patches).
Linux makes an OK home firewall. But I wouldn't use it anywhere near a business.
We use FreeBSD 4.9 on Pentium 166 MHz systems with 128 MB RAM using IPFW to server secondary schools with just under 300 student computers. Haven't had any problems yet with network slowdowns or dropoffs or anything. These are on T1s in the remote schools, and 8 Mbit cable in town.
(I had problems keeping a similar box running Linux and IPTables working on my home wireless T1-equiv link.)
Close. The Pentium-M uses the Pentium-III core, with some P4 stuff (better branch prediction, slightly deeper pipeline, etc) tacked on top. The Pentium-M does not use the NetBurst architecture of the P4. There's a very nice, in-depth look at the Pentium-M over on Ars Techinca.
Dude, you are so far out in left field, you may as well start planting daisies.
The new license does *NOT* apply to any of the XFree86 libraries. Hence, there *ARE NO CHANGES* in the way things work, regarding linking to XFree86 libraries. IOW, NOTHING HAS CHANGED, in this regard.
The reason for the bruhaha is nothing more than laziness on the part of the various distros. They don't want to take the time to put "This project includes software from the XFree86 Project." into any of the end-user documentation. IOW, nobody wants to give credit to the XFree86 Project, yet they all want to use software from the XFree86 Project.
Been testing ClamAV + Amavisd-new + SpamAssassin + Postfix + Courier-IMAP here.
:)
In the past 4 weeks, it's managed to block:
244 virus messages
416 spam messages
correctly tagged 450 messages as possible spam (kill setting is low right now while I test the system).
And that's just on my 3 e-mail accounts. I haven't put this into testing inside the department yet.
The current database scans for more than 20,000 viruses and variants.
UnitedLinux is dead. Has been for a couple months now. And they never even got to the point of releasing 1.0.
The problem isn't that Intel is creating an AMD64-compatible chip. That's a good thing.
The problem is that Intel is not crediting AMD for all their work on the AMD64 architecture and instructions. All the Intel literature gives the impression that Intel created the whole 64-bit x86 ISA. This is just wrong, underhanded, and petty.
It was a joke. Intel released the i386 to the world when the "advanced" 16-bit DOS and 16-bit OS/2 were around. No 32-bit OS in sight. It wasn't until several years later that NT (the first truly 32-bit Windows) was released, and several more until the hybrid, consumer-level Windows 95 hit the market (OS/2 was 32-bit long before, but didn't make much of a dent).
But, their "main" reason for not releasing a 64-bit chip was because there was no 64-bit capable OS. Doesn't really follow from their past CPU releases, now does it?
This is a great little util. I really like the burn-in tests, and the fact that it can test the different RAM slots independently (on most mobos). Trying to figure out which stick of RAM is bad in a 4 GB system using memtest86 takes too long, and involves too many stops to replace the RAM chip. This way, I just let it run overnight and remove the faulty chip when it's done.
The other tests are nice, and useful as well. And having it all on a bootable floppy is nice, as you don't have to worry about having a working OS on the system.
Use it in place of your BBQ. :) Cook an entire roast pig in less than 5 minutes. Tim Allen would love this, and you'd probably get a spot on The Man Show as well. :)
The GENERIC kernelk comes with support for virtually everything, except sound. However, any device driver that is not explicitly compiled into the kernel is available as a module (including sound). So, it's just a matter of browsing through /boot/kernel/*.ko or /modules/*.ko and loading the appropriate driver.
/boot/loader.conf to have the module loaded at boot time automatically, or you can compile a custom kernel with that driver built in.
Once you know which driver is needed, you can either edit
The Windows GUI shell (or window manager) is called explorer.exe. This program, and the associated libs, control the entire GUI environment.
There have been replacement shells since the release of Windows 95 and NT 4. Some are quite nice (darkstep / litestep), some are nifty (98Lite) some are just bizarre. But, there are still plenty out there to choose from.
The only interesting thing to be gleaned from the source of explorer.exe and libs would be how they get things like the RUN dialog, or system folder like My Documents to work. These are usually the bits you lose when you run a replacement shell.