I agree. At least the sound hardware was autodetected, which is a lot better than the old days. The new hotplug package works wonders on my laptop (except for the soft-modem), and my rc.modules file is completely empty. Even my orinoco card automatically grabs an IP address with no extra configuration.
Arts, which is part of KDE, does a passable job of duplexing cards that lack mixing in hardware or in the driver. One can just run 'artsdsp xmms' with xmms running with the OSS driver, and the sound will automagically be mixed by arts to the sound card. Arts does seem to use about 10% processor though for this functionality. Esound is supposed to do this too, but I haven't looked closely. Both are included with Slackware.
Swaret's dependency checking is actually pretty neat. For some dependencies, it is able to get a list of package relations from an external site maintained by the swaret project. For other dependencies, does something like an ldd on the binaries in a package to determine which libraries are missing. Sometimes, it can then deduce which packages need to be installed from this information. If not, at least you have some clue as to what is missing.
As for building software on Slack, usually 'configure' catches any missing dependencies before compiling begins. One nice thing about Slackware is there are no '-dev' packages. Just install the compiler, and all of the necessary include files are already there from the other packages.
You can get it and a lot more Slackware extra packages here:.
If you really want it in the base distribution, just ask Patrick. He is usually prompt and if you make a good case for a package, he will add it. It also helps if you can give some built tips for particularly onery packages.
OK, then how about benchmarking in Linux or FreeBSD. They both support Direct Rendering Manager. I'm sure that a vendor arms race would be a welcome sight in the free operating system arena.
Benchmarkers can just always rename their benchmark programs to something else when testing. Isn't this how a lot of recent driver optimizations were discovered in the first place? How about a benchmark installer that installs a differently-named executable every time.
Not to speak of security, but I have tried a couple of these small firewall boxes, a linksys and an SMC, up against Roadrunner's DHCP and SBC DSL's PPPoE connections. The biggest problems I had were that these boxes would drop connection big time if there was any kind of service ripple, and more often were unable to reconnect without restarting the box (power cycle or via the web interface). The SMC couldn't run for more than a couple of days over PPPoE without a reset.
Both FreeBSD and Linux have proven to be much more reliable against sometimes quirky network conditions. My current machine will have a new IP address and have updated my dyndns.org entries within 30 seconds of plugging in my DSL modem.
If you're going to get a firewall/router appliance, get one that has something like Linux or BSD at its core.
We have two ESX servers running at work. They both came with Redhat as the core OS. The Linux kernel appears to just use a small chunk of memory and is modified to allow processes to grab memory external to their normally allowed virtual address space, while the ESX server software apparently manages the rest of the memory itself. But, the server also runs as a Linux process. It definitely relies in Linux's driver support to support the underlying real hardware. It's neat; they have more than just the GNU toolchain in the Linux instance; there is Perl too, and everything else you would expect.
I think that a great potential project for OpenOffice would be to produce standalone filtering programs like those included with NetPBM. If there were doc2oo and oo2doc programs (xls2oo, etc.), every other package that wanted to support MS Office or any other formats supported by OpenOffice could simply support the OpenOffice format, and call the OpenOffice filters on import or export. It would also be great for batch conversions.
But, if there were no copyright and someone took your code and incorporated it into a closed project, then if you were to happen upon that code later (say by reverse engineering, a leak, someone working on the project release it, intentionally or not), you could use it anyway, since the closed project would also have no copyright, and no right to protect the closed project either. GPL uses copyright to defend against copyright, essentially. That is why it is sometimes called Copyleft. It does work both ways.
Then again, KDE also works in *BSD, Solaris, HP-UX, and even Windows, to name a few. Writing kernel modules that work for every one of these systems would be a bit of a hassle, no? It might not even be possible in a few of these.
If someone were to implement all of these systems in the kernel, then KDE/GNOME, etc. can already them. In the mean time, this seems to be the best compromise between functionality and portability.
I thought that it was interesting that all of the Oregon proponents either submitted HTML or LaTeX generated PDFs, both of which were extremely fast-loading and good looking. The BSA's response looked like scanned-in faxes turned into a PDF, and the other opponents' responses were likewise bloated PDFs.
What does this say about the quality of the software used to create these responses, assuming that the authors all used the sorts of software they endorse?
It still uses a 64 bit address pointer register, and all addresses are 64 bit with the Opteron, code-wise. This makes it simple to, down the line, add more physical bits and have code automatically be able to address more memory. Integer sizes default to 32bit with it, for code size (most programs only need 32 bit), but a long will be a lot faster to deal with if code needs it.
In a color TV, there are three types of phosphors, red, green and blue. The electron guns (or gun in a trinitron) must be aligned so that they hit the correct phosphors. Otherwise, the colors look off. The guns are typically aligned with an appeture mask or grille, which snaps the electron streams into place above their respective phosphors.
A black-and-white TV has only one type of phosphor, so it is not as important that the electron streams hit the correct, absolute position on the screen. The screen is uniformly coated, and I don't believe there is an appeture screen on these types of screens.
So, what happens when you hold a magnet to the screen? For one, you deflect the electron streams, so you get a temporarily distorted image, and the colors are off because the electron streams are pointing to the wrong phosphors. With B/W, it just doesn't matter; a phosphor is a phosphor.
Additionally, a powerful magnet can permanently distort or magnetize the metal appeture mask/grille, causing permanent damage the the screen's ability to align electron streams to the appropriate phosphors.
And that's it. I may have misspelled appeture. Oh well.
I have a Compaq Prosignia VS from 1994. It has a 'system partition', which stores EISA profiles, drivers, diagnostics, the setup programs, etc. It runs dos, and is built right in.
If you want NTFS support for FreeBSD, simply find a source of unencumbered documentation on that FS and let the developers know where you found it. Having trouble? I thought so!
NTFS is intentionally underdocumented, so most attempts to support it in other OS's have been mostly reverse-engineering attempts. You could sign an NDA, but probably wouldn't be able to write free code with that information. Do not blame FreeBSD for not supporting undocumented features of another OS.
If you have an example of any non-Microsoft OS that can install on NTFS, please prove me wrong!
TridiaVNC is open source and freely distributed under the GNU General Public License. You are free to install, customize, integrate, and enhance TridiaVNC to meet your specific needs.
Slashdot Mirror
I agree. At least the sound hardware was autodetected, which is a lot better than the old days. The new hotplug package works wonders on my laptop (except for the soft-modem), and my rc.modules file is completely empty. Even my orinoco card automatically grabs an IP address with no extra configuration.
Arts, which is part of KDE, does a passable job of duplexing cards that lack mixing in hardware or in the driver. One can just run 'artsdsp xmms' with xmms running with the OSS driver, and the sound will automagically be mixed by arts to the sound card. Arts does seem to use about 10% processor though for this functionality. Esound is supposed to do this too, but I haven't looked closely. Both are included with Slackware.
Swaret's dependency checking is actually pretty neat. For some dependencies, it is able to get a list of package relations from an external site maintained by the swaret project. For other dependencies, does something like an ldd on the binaries in a package to determine which libraries are missing. Sometimes, it can then deduce which packages need to be installed from this information. If not, at least you have some clue as to what is missing.
As for building software on Slack, usually 'configure' catches any missing dependencies before compiling begins. One nice thing about Slackware is there are no '-dev' packages. Just install the compiler, and all of the necessary include files are already there from the other packages.
You can get it and a lot more Slackware extra packages
here:.
If you really want it in the base distribution, just ask Patrick. He is usually prompt and if you make a good case for a package, he will add it. It also helps if you can give some built tips for particularly onery packages.
OK, then how about benchmarking in Linux or FreeBSD. They both support Direct Rendering Manager. I'm sure that a vendor arms race would be a welcome sight in the free operating system arena.
Benchmarkers can just always rename their benchmark programs to something else when testing. Isn't this how a lot of recent driver optimizations were discovered in the first place? How about a benchmark installer that installs a differently-named executable every time.
Not to speak of security, but I have tried a couple of these small firewall boxes, a linksys and an SMC, up against Roadrunner's DHCP and SBC DSL's PPPoE connections. The biggest problems I had were that these boxes would drop connection big time if there was any kind of service ripple, and more often were unable to reconnect without restarting the box (power cycle or via the web interface). The SMC couldn't run for more than a couple of days over PPPoE without a reset.
Both FreeBSD and Linux have proven to be much more reliable against sometimes quirky network conditions. My current machine will have a new IP address and have updated my dyndns.org entries within 30 seconds of plugging in my DSL modem.
If you're going to get a firewall/router
appliance, get one that has something like Linux or BSD at its core.
We have two ESX servers running at work. They both came with Redhat as the core OS. The Linux kernel appears to just use a small chunk of memory and is modified to allow processes to grab memory external to their normally allowed virtual address space, while the ESX server software apparently manages the rest of the memory itself. But, the server also runs as a Linux process. It definitely relies in Linux's driver support to support the underlying real hardware. It's neat; they have more than just the GNU toolchain in the Linux instance; there is Perl too, and everything else you would expect.
I think that a great potential project for OpenOffice would be to produce standalone filtering programs like those included with NetPBM. If there were doc2oo and oo2doc programs (xls2oo, etc.), every other package that wanted to support MS Office or any other formats supported by OpenOffice could simply support the OpenOffice format, and call the OpenOffice filters on import or export. It would also be great for batch conversions.
But, if there were no copyright and someone took your code and incorporated it into a closed project, then if you were to happen upon that code later (say by reverse engineering, a leak, someone working on the project release it, intentionally or not), you could use it anyway, since the closed project would also have no copyright, and no right to protect the closed project either. GPL uses copyright to defend against copyright, essentially. That is why it is sometimes called Copyleft. It does work both ways.
Then again, KDE also works in *BSD, Solaris, HP-UX, and even Windows, to name a few. Writing kernel modules that work for every one of these systems would be a bit of a hassle, no? It might not even be possible in a few of these.
If someone were to implement all of these systems in the kernel, then KDE/GNOME, etc. can already them. In the mean time, this seems to be the best compromise between functionality and portability.
I thought that it was interesting that all of the Oregon proponents either submitted HTML or LaTeX generated PDFs, both of which were extremely fast-loading and good looking. The BSA's response looked like scanned-in faxes turned into a PDF, and the other opponents' responses were likewise bloated PDFs.
What does this say about the quality of the software used to create these responses, assuming that the authors all used the sorts of software they endorse?
They don't even own the trademark. That belongs to the Open Group according to the OSI position paper linked by Bruce Perens above.
Did you see this post from yesterday? I was very impressed and surprised at how well neural inputs work today.
It still uses a 64 bit address pointer register, and all addresses are 64 bit with the Opteron, code-wise. This makes it simple to, down the line, add more physical bits and have code automatically be able to address more memory. Integer sizes default to 32bit with it, for code size (most programs only need 32 bit), but a long will be a lot faster to deal with if code needs it.
In a color TV, there are three types of phosphors, red, green and blue. The electron guns (or gun in a trinitron) must be aligned so that they hit the correct phosphors. Otherwise, the colors look off. The guns are typically aligned with an appeture mask or grille, which snaps the electron streams into place above their respective phosphors.
A black-and-white TV has only one type of phosphor, so it is not as important that the electron streams hit the correct, absolute position on the screen. The screen is uniformly coated, and I don't believe there is an appeture screen on these types of screens.
So, what happens when you hold a magnet to the screen? For one, you deflect the electron streams, so you get a temporarily distorted image, and the colors are off because the electron streams are pointing to the wrong phosphors. With B/W, it just doesn't matter; a phosphor is a phosphor.
Additionally, a powerful magnet can permanently distort or magnetize the metal appeture mask/grille, causing permanent damage the the screen's ability to align electron streams to the appropriate phosphors.
And that's it. I may have misspelled appeture. Oh well.
But the electricity has to come from somewhere. That is the problem with this idea.
I have a Compaq Prosignia VS from 1994. It has a 'system partition', which stores EISA profiles, drivers, diagnostics, the setup programs, etc. It runs dos, and is built right in.
This still seems like a rehash.
It also supports ogg/vorbis files. Ogg Traffic
If you want NTFS support for FreeBSD, simply find a source of unencumbered documentation on that FS and let the developers know where you found it. Having trouble? I thought so!
NTFS is intentionally underdocumented, so most attempts to support it in other OS's have been mostly reverse-engineering attempts. You could sign an NDA, but probably wouldn't be able to write free code with that information. Do not blame FreeBSD for not supporting undocumented features of another OS.
If you have an example of any non-Microsoft OS that can install on NTFS, please prove me wrong!
You would have shot him in your humble opinion? Come on, how can you have an opinion about something you do yourself? How is this humble anyway?
Except that they now have one.
I saw a similar boat-load of remode-controlled mini-racing cars at Home Depot for $12 each. I don't remember the brand, but they looked like fun.
I believe that a lot of imporant free software sites were hosted by this university. Hence, its relevance here.
From the website:
FedScope v1 was released on May, 12, 2002
Because, according to the TridiaVNC web page:
TridiaVNC is open source and freely distributed under the GNU General Public License. You are free to install, customize, integrate, and enhance TridiaVNC to meet your specific needs.