That would be a really nice to have, if a company could afford it... but that's just talking about SQL Server alone. The SQLSlammer worm also impacts MSDE, which is a slimmed-down version of SQL Server (most likely the Developer Edition) that is a step up from using a Jet and/or an MS-Access database.
MSDE is required for those who want to do some development or for those running Visio 2000 Enterprise Edition along with the network device discovery tools provided for device inventory and device data. There are probably other things out there that use MSDE in part or in whole. Just think if someone had it on a personal laptop and brought it into their work, it gets affected somehow and takes down the rest of the servers because they haven't fully tested or get third-party vendor add-ons for SQL Server support for SP3.
I'm not talking about Service Packs... but hotfixes, like the one for MS02-056. Of course, they provide an additional tool to help automate the install process of hotfixes (here) that make it a bit easier. But before that was available, take a look at the previous cumulative patches for SQL Server 2000 and read the readme file for the install process. Not as easy as installing a Service Pack, no?
Okay... I butchered that first sentence. It should have been:
There isn't a way to get SQL Server patches from Windows Update...
The same is also true for SQL Server 7.0. At least Exchange 5.5 provides a decent hotfix delivery method that will automatically install the updated binaries and DLLs. I haven't had any experience with Oracle and other database systems, but how do the database server update steps compare to the ones for SQL Server?
There isn't only no way to get SQL Server patches from Windows Update, but (as the parent mentioned), the steps required to update SQL Server and the Desktop Engine (MSDE) is a royal bitch and some.
For example, to apply any hotfixes or cumulative patches for SQL Server 2000, you must download the package, extract it, backup the SQL Server install directory and databases, manually copy over DLL files and other updated binaries, execute the SQL query files included in the patch (one at a time, in a certain order... MSDE users need to use the command line interface for it since there is no GUI provided), then pray that everything is okay and start SQL back up.
Bluetooth could be added into the device via a second chip and IrDA connection could be handled by one of the two serial ports that the 405LP can drive.
I just dugged through the OpenBSD and NetBSD websites to see if there are any mentions of SysV or SCO and it looks like NetBSD does provide binary emulation/compatibility for IBCS2 systems (including SCO Unix and SCO Xenix) under the i386 section on this page.
I didn't see anything for OpenBSD, but OpenBSD developers and users can feel free to pipe in on this matter.
I believe that is the case, but FreeBSD (and possibly NetBSD and OpenBSD) include a System V compatibility layer that allows programs to use System V calls via shims and a kernel module. That could be the code that SCO is aiming at.
FreeBSD includes software compatibility layers (such as Linux, etc.) that also includes some System V shims and code that could be targetted by SCO. I believe the kernel module that could be in question is svr4.ko along with the stuff under/usr/src/sys/svr4.
NetBSD and OpenBSD may also have the same code or code derivatives in their base system's source.
I believe it was 4.4Lite that was the result of the BSD vs. AT&T court case, which in itself was a re-write to be "clean" of any AT&T source code... or at least clean enough for AT&T to allow it's distribution. I could be wrong though...
I don't remember where I read this, but I don't think IBM wants to get back into the market of producing complete handhelds (say like they did when they sold a re-packaged OEM Palm). Rather, they would provide kits for other companies to build custom handhelds either for specific areas (kind of like Symbol) or for those who want to compete in the Linux PDA side of things.
Still, it's nice to see that there is another architecture entering into the world of handhelds and PDAs... even if it doesn't immediately result in additional retail Linux-based PDAs.
Considering that the 405LP that is being used in the reference design could be considered an embedded processor, it's also less complex than say the lowest power consumption x86 or x86-compatible processor. It's also hard to find a x86 processor that has a typical power consumption of under a watt and has all of the features of the 405LP, plus fit into the space requirements of handhelds and other small devices.
Price isn't as much of a concern since you would normally trade cost for portability, and vice versa.
The other benefit of the PPC architecture is the fact that you don't have the kludge of an ISA that is the x86 ISA... meaning that developing apps for a PPC (or an ARM) architecture may not be as bad... and I think code written for the PPC architecture can run on any other PPC processor, provided that you don't include processor specific extensions.
You can always use CVSup to pull down the latest version of the source branch (RELENG_5 or RELENG_5_0 I think, but check the FreeBSD Handbook just to make sure) and do a make world on the system once the patch is available in the source tree.
Not when using Constant Bitrate (CBR) MP3 encoding, or Average Bitrate (ABR) encoding with a forced minimum bitrate level. Both ABR, without a forced minimum bitrate, and Variable Bitrate (VBR) should be able to encode silence at the lowest possible bitrate for MP3 (16 or 32kbps I think).
So a one minute 128kbps MP3 file will still soak up 1MB of space after compression.
According to the second paragraph of the press release:
A pioneer in DVD technology and products, Toshiba has been a driving force in consumer adoption of the DVD format and continues to demonstrate a commitment to offering advanced configurations of the technology. Most recently, the company introduced the industry's first DVD-RAM/HDD (80G) recorder, model RD-X2, in response to consumers' growing interest in recording programs on a hard disk drive and storing on a large capacity digital disc. Toshiba also offers a full line of DVD players with features such as ColorStream Pro® progressive scan, Digital Photo Viewer and DVD-Audio playback (all features not available on all models).
It looks like it's both a TiVo DVR plus a DVD-RAM (it doesn't say if it can support standard DVD-R or if it's just DVD-RAM) recorder. Why DVD-RAM? I think it's allows one to delete a file from the disc and be able to record data into that spot like you could with a hard drive, rather than burning in sessions and finalizing the sessions... which can be a big PIA at times.
Re:Signs of desperation?
on
New SGI Altix 3000
·
· Score: 2, Interesting
SGI did make Intel-based workstations that ran Windows NT/2000 that used all standard ports (ATX motherboard layout, Rambus memory, AGP video, et al)... particularly the 550 workstation. They also made several workstation lines that used proprietary memory and graphics subsystem that also ran Windows NT.
For a time... didn't SGI repackage Intergraph workstations as their own? They also had an Itanium 1 workstation that was nearly identical to HP's and Dell's Itanium 1 workstation... but I don't think many of those were ever made.
copy what one company did with their Novell server... put a wall around it! That'll not only hide the not-always-so-good-looking machine but also keep it fairly secured;-)
If you have an account with Amazon.com and are logged in, browse to the CD that you have and below the "Music Information" section on the left, there should be "Rate This Item". Rate it and check "I own it" then submit.
I've done that with a couple of CDs that I have (that they sell anyway) and found a couple of additional CD recommendations that ended up being fairly good. That's how I racked up all of the techno compilation or box set CDs... well, purchased them from the UK version of Amazon anyway;-)
CDNow.com is actually handled by Amazon.com nowadays (even though it's business backend is still handled by one of the big media online units). The switch-over happened a handful of weeks ago I think.
Nik Clayton of the FreeBSD project has a page with links to resources on clustering FreeBSD. Some of the links are dead, but the ones that work should give you enough information about clustering FreeBSD (and possibly other BSD operating systems).
It's probably not as elegant or as well known as Beowulf clustering, but it has been done:)
My old Pentium 233MHz computer came with USB ports in a bracket that I could screw into one of the expansion slot covers. That machine was purchased before the iMac was made. Several motherboard manufacturers had USB controllers on their motherboards, but either did or didn't have it as part of the ATX backplane.
I think it's more appropriate to say that the iMac was the product that brought USB devices and peripherals into the mainstream market. The USB spec was worked on by Intel, Microsoft and other companies before the iMac came out... what Apple did was to make that the device connector and bus of choice, replacing SCSI, parallel, serial and ADB ports/busses with a simple and hot-swappable standard.
Now if you had replaced "USB" with "FireWire" (or IEEE 1394) in your first sentence, I would wholeheartedly agree.
Microsoft includes a fairly stripped down version of the disk defragmenter software that Executive Software produces and it does have it's limitations (like not being able to defrag system files, the master file tables nor the paging files, unable to defrag NTFS partitions with a cluster size of over so many Kbytes, etc.) There are many times that I wish I had the full version of their defrag tool at times since some of the database servers that I work with have fairly large file system cluster sizes which cannot be defragged.
The Backup tool included in Windows 2000 and XP are both developed by Veritas and they are doing fairly well... though they like to change their product grouping and strategies about as often as CA does. Just like the included defrag tool, Backup is fairly functional but still doesn't compare to the full blown Backup Exec counterpart.
Slashdot Mirror
That would be a really nice to have, if a company could afford it... but that's just talking about SQL Server alone. The SQLSlammer worm also impacts MSDE, which is a slimmed-down version of SQL Server (most likely the Developer Edition) that is a step up from using a Jet and/or an MS-Access database.
MSDE is required for those who want to do some development or for those running Visio 2000 Enterprise Edition along with the network device discovery tools provided for device inventory and device data. There are probably other things out there that use MSDE in part or in whole. Just think if someone had it on a personal laptop and brought it into their work, it gets affected somehow and takes down the rest of the servers because they haven't fully tested or get third-party vendor add-ons for SQL Server support for SP3.
I'm not talking about Service Packs... but hotfixes, like the one for MS02-056. Of course, they provide an additional tool to help automate the install process of hotfixes (here) that make it a bit easier. But before that was available, take a look at the previous cumulative patches for SQL Server 2000 and read the readme file for the install process. Not as easy as installing a Service Pack, no?
Okay... I butchered that first sentence. It should have been:
There isn't a way to get SQL Server patches from Windows Update...
The same is also true for SQL Server 7.0. At least Exchange 5.5 provides a decent hotfix delivery method that will automatically install the updated binaries and DLLs. I haven't had any experience with Oracle and other database systems, but how do the database server update steps compare to the ones for SQL Server?
There isn't only no way to get SQL Server patches from Windows Update, but (as the parent mentioned), the steps required to update SQL Server and the Desktop Engine (MSDE) is a royal bitch and some.
For example, to apply any hotfixes or cumulative patches for SQL Server 2000, you must download the package, extract it, backup the SQL Server install directory and databases, manually copy over DLL files and other updated binaries, execute the SQL query files included in the patch (one at a time, in a certain order... MSDE users need to use the command line interface for it since there is no GUI provided), then pray that everything is okay and start SQL back up.
Which they acquired when they bought USRobotics (which has spun-off again, no?).
HP spun off Agilent. Lucent spun-off Agere and maybe another one.
Then you have AT&T trying to break itself up into three, but then AT&T Broadband got eaten up by Comcast.
Well, Red Hat is using PostgreSQL for their Red Hat Database package and presumably would provide support for it. You can also find support partners for PGSQL at http://www.pgsql.com/partnerlinks/.
Bluetooth could be added into the device via a second chip and IrDA connection could be handled by one of the two serial ports that the 405LP can drive.
I didn't see anything for OpenBSD, but OpenBSD developers and users can feel free to pipe in on this matter.
I believe that is the case, but FreeBSD (and possibly NetBSD and OpenBSD) include a System V compatibility layer that allows programs to use System V calls via shims and a kernel module. That could be the code that SCO is aiming at.
FreeBSD includes software compatibility layers (such as Linux, etc.) that also includes some System V shims and code that could be targetted by SCO. I believe the kernel module that could be in question is svr4.ko along with the stuff under /usr/src/sys/svr4.
NetBSD and OpenBSD may also have the same code or code derivatives in their base system's source.
I believe it was 4.4Lite that was the result of the BSD vs. AT&T court case, which in itself was a re-write to be "clean" of any AT&T source code... or at least clean enough for AT&T to allow it's distribution. I could be wrong though...
I don't remember where I read this, but I don't think IBM wants to get back into the market of producing complete handhelds (say like they did when they sold a re-packaged OEM Palm). Rather, they would provide kits for other companies to build custom handhelds either for specific areas (kind of like Symbol) or for those who want to compete in the Linux PDA side of things.
Still, it's nice to see that there is another architecture entering into the world of handhelds and PDAs... even if it doesn't immediately result in additional retail Linux-based PDAs.
Considering that the 405LP that is being used in the reference design could be considered an embedded processor, it's also less complex than say the lowest power consumption x86 or x86-compatible processor. It's also hard to find a x86 processor that has a typical power consumption of under a watt and has all of the features of the 405LP, plus fit into the space requirements of handhelds and other small devices.
Price isn't as much of a concern since you would normally trade cost for portability, and vice versa.
The other benefit of the PPC architecture is the fact that you don't have the kludge of an ISA that is the x86 ISA... meaning that developing apps for a PPC (or an ARM) architecture may not be as bad... and I think code written for the PPC architecture can run on any other PPC processor, provided that you don't include processor specific extensions.
You can always use CVSup to pull down the latest version of the source branch (RELENG_5 or RELENG_5_0 I think, but check the FreeBSD Handbook just to make sure) and do a make world on the system once the patch is available in the source tree.
Not when using Constant Bitrate (CBR) MP3 encoding, or Average Bitrate (ABR) encoding with a forced minimum bitrate level. Both ABR, without a forced minimum bitrate, and Variable Bitrate (VBR) should be able to encode silence at the lowest possible bitrate for MP3 (16 or 32kbps I think).
So a one minute 128kbps MP3 file will still soak up 1MB of space after compression.
SGI did make Intel-based workstations that ran Windows NT/2000 that used all standard ports (ATX motherboard layout, Rambus memory, AGP video, et al)... particularly the 550 workstation. They also made several workstation lines that used proprietary memory and graphics subsystem that also ran Windows NT.
For a time... didn't SGI repackage Intergraph workstations as their own? They also had an Itanium 1 workstation that was nearly identical to HP's and Dell's Itanium 1 workstation... but I don't think many of those were ever made.
copy what one company did with their Novell server... put a wall around it! That'll not only hide the not-always-so-good-looking machine but also keep it fairly secured ;-)
Just hope that they do not use Macrovision or some other "watermark" that doesn't allow you to record what comes out of the video out on the unit.
If you have an account with Amazon.com and are logged in, browse to the CD that you have and below the "Music Information" section on the left, there should be "Rate This Item". Rate it and check "I own it" then submit.
;-)
I've done that with a couple of CDs that I have (that they sell anyway) and found a couple of additional CD recommendations that ended up being fairly good. That's how I racked up all of the techno compilation or box set CDs... well, purchased them from the UK version of Amazon anyway
CDNow.com is actually handled by Amazon.com nowadays (even though it's business backend is still handled by one of the big media online units). The switch-over happened a handful of weeks ago I think.
It's probably not as elegant or as well known as Beowulf clustering, but it has been done :)
It's probably running off of solar power... and it isn't sunny out here right now.
:)
It's funny, laugh!
My old Pentium 233MHz computer came with USB ports in a bracket that I could screw into one of the expansion slot covers. That machine was purchased before the iMac was made. Several motherboard manufacturers had USB controllers on their motherboards, but either did or didn't have it as part of the ATX backplane.
I think it's more appropriate to say that the iMac was the product that brought USB devices and peripherals into the mainstream market. The USB spec was worked on by Intel, Microsoft and other companies before the iMac came out... what Apple did was to make that the device connector and bus of choice, replacing SCSI, parallel, serial and ADB ports/busses with a simple and hot-swappable standard.
Now if you had replaced "USB" with "FireWire" (or IEEE 1394) in your first sentence, I would wholeheartedly agree.
Just my thoughts and my US$0.01.
Microsoft includes a fairly stripped down version of the disk defragmenter software that Executive Software produces and it does have it's limitations (like not being able to defrag system files, the master file tables nor the paging files, unable to defrag NTFS partitions with a cluster size of over so many Kbytes, etc.) There are many times that I wish I had the full version of their defrag tool at times since some of the database servers that I work with have fairly large file system cluster sizes which cannot be defragged.
The Backup tool included in Windows 2000 and XP are both developed by Veritas and they are doing fairly well... though they like to change their product grouping and strategies about as often as CA does. Just like the included defrag tool, Backup is fairly functional but still doesn't compare to the full blown Backup Exec counterpart.
According to the FreeBSD Handbook under Appendix A, section 6, the tag that you want is: *default tag=.