Well, a writer for these would probably be small and cheap, so a factory mass-producing many pre-written memory modules could have lots of them. Also, this solves the problem (or whatever it is) of how to sign each copy with a unique fingerprint so that copies can be traced.
You can have stable, or you can have bleeding-edge. Debian gives you both options (three, actually).
Testing and unstable aren't real distributions with real security updates. It seems to me that Debian doesn't provide any real middle ground between using really old software where most bugs have hopefully been found, and using new software that actually have the new features you need or want.
This is nice, but everyone won't agree on using Debian as the base. It is developed by the right kind of organization for this and it's stable, but it's old. Like, Mozilla 1.0.0. Hello? Old GNOME and KDE as well.
Sure, I can use unstable, but that's not a good solution. Using another distribution that's based on a snapshot of Debian unstable could work, though. (I suppose it could be called UserLinux.)
Are dpkg installations interactive or does it just seem that way? I like that way rpm:s install without asking any questions and just give me a basic config file I can edit. Now that I have apt-rpm I'm pretty happy with my RPM-based distro. It's got recent, modern software, it's user-friendly and it works well. Why start over with Debian?
There's KRB5/GSSAPI/IMAP support in Ximian Evolution nowadays. You need version 1.2.4 or later. It's enabled in the binaries for RHL9 from Ximian. A nice single-sign-on mail solution for sites with a Kerberos infrastructure.
This would mean that there would be a database of all copyrighted works older than 50 years. In other words, if you have access to some potentially copyrighted work that you know is older than 50 years, you can simply look for it in the database. If it's not there, you're free to republish it!
Not to mention that many users of consumer level NATing devices (Cable/DSL routers) do so for financial reasons, not out of necessity. Why pay your ISP for another IP address when you can run upwards of 200 machines on the one you already have.
An ISP that charge more for one/48 or even two/128 than it charges for one/128 is a monopolist company and should be discorporated.
I have to secure each and every host on my network
Well, that's great! That means you don't need a firewall. Instead you'll have full internet access. Also, your system will be more secure in case you have an intruder inside you network. (That is, someone who rooted one of your hosts or someone with physical access to the network.)
Yeah, sure, the SIM card is just another way of authenticating to the network so you can log on and get you personal phone number. If you have some kind of secret code instead, that's fine. (Well, I suppose SIM cards are more secure, but I wouldn't know.)
The problem here is that the previous owner of the phone signed up to these things and that the new owner is forced to use the same telephone number as the previous owner.
The new owner of the phone should be able to put his own GSM-style SIM card with his own telephone number in the phone. By mapping telephone numbers to SIM cards instead of to telephones the buyer of a used phone don't have to worry about who the previous owner of the phone gave away his phone number to. (And as an added bonus he gets to keep is old number.)
I guess my questions is simple, how do these IDE based raids with SCSI interfaces work?
It simple, but it's not just a SCSI to IDE converter.
A IDE RAID with a SCSI interface is a box with six or more slots for removable harddisks, six or more IDE interfaces, a CPU (or some other kind of microcontroller) running RAID software, a front panel (LCD and buttons), a serial port and a SCSI interface. The panel and serial port interfaces are used for things like setting the SCSI ID and telling the RAID controller what kind of RAID to use (0, 1, 5) and whether or not to use one of the disks as a standby spare disk (so that it can start rebuilding the RAID-5 set immediately if one disk fails.
All the computer sees is one gigantic SCSI disk. No special software or configuration is needed, even if the computer is booting from it.
There are RAID systems that make use of cheap IDE disks but still have a SCSI connection to computer. Until consumers wake up and start demanding that IDE and SCSI disks cost almost the same, I think this is an ideal solution. It works well and it's both fast and cheap.
For instance, users on a 56k modem could listen to the same multicast stream as a broadband user (ie, no need to send out multiple, separate versions from the source)-- this assumes the presence of routers (or conversion boxes) capable of doing the peeling as needed.
Actually, it doesn't require specific Vorbis support in the netword nodes. With IPv6, a multicast stream can be divided into layers, where high-bandwidth receivers get the packets from all layers while low-bandwidth receivers only get the "bottom" layers which hold enough info to recreate low-quality audio and video. The routers will use the layer info to decide which packets to throw away during congestion.
I suppose it's possible to emulate most of this in IPv4 multicast using several streams, but it's not as automatic.
One of the websites I helped build is broken in 1.2 (just noticed it yesterday). This was working fine in 1.2b, as well as in a homebuilt CVS version somewhere in the cycle leading up to 1.2.
I see... Mod parent up and mod parent.parent down.
I think a "Release Candidate" should have been put out, which when tested for a while should have become 1.2 final without any further changes.
If 1.2 had been called 1.2rc1 and had been released as 1.2, it would still have had this bug.:-)
I think the basic problem is that 1.0.1 and 1.1 works so well that few people bothered to test the 1.2 alpha and beta. Hence serious bugs showing up in the release.
Because RDP is a better protocol than X -- lower bandwidth and less percieved user latency.
X works fine at a megabit per second or more and it works perfectly over IEEE802.11b.
It's the same reason Sun's 'smart' terminals don't run X11.
No! The SunRays are really quite slow. Not at all much faster than running encrypted X over my DSL line at home to the server at work. X11 have some problems that make it less than optimal as a SunRay protocol, but it's not about speed, and it's nothing that couldn't be fixed, really. I'd say the reason has something to do with the "advantages" of a proprietary protocol.
Mathematica might help in college, but what about after graduation? Nobody in the Real World uses Mathematica. MatLab is the only sane choice here.
They are totally different things! I haven't really used Mathematica so I can tell wheter it is good for learning math, but Matlab certainly isn't. Matlab is basically just a programming language made for dealing with largs data sets. How do you use that to teach children math?
And if the kids are supposed to learn how to code, give them a well-designed language, instead of that awful crap called Matlab. Say, LISP. Or Perl! And BASH.
To manufacture physical goods, you get yourself a factory for a million bucks, hire some people and buy some machinery, raw material and parts. Then you buy some patent licenses. They will cost you, but not as much as all the other stuff.
To write and distribute software, you get a computer, a fast internet connection and a website, all for around a thousand bucks a year. Since it's all so cheap, and you like coding, you just write stuff that benefits us all (everyone uses free software, whether they know it or not) and release it for free. Then you start to get nice letters from patent lawyers. Or you're selling your software, but you can't get a decent profit because all the big boys with lots of patents know how to use the system to make their competitors starve to death.
See? Patents in all areas, be it steam engines or audio compression algorithms, do both good and bad. They encourage innovation, but they also discourage the implementation of already existing ideas. With the above example I'd like to show that the negative effect of patents are a much larger factor in the software area than in other areas. It costs too much to get licenses, if they are at all for sale. The patents owners have too much power, beacause patents last for at least 20 years, in a fast-moving business that's only 50 years old. Software patents that expires after, say, two years would be OK.
Slashdot Mirror
Se also a recent speech (scroll down a bit) by Stephen Hawking on string theory and the origin of the universe.
Well, a writer for these would probably be small and cheap, so a factory mass-producing many pre-written memory modules could have lots of them. Also, this solves the problem (or whatever it is) of how to sign each copy with a unique fingerprint so that copies can be traced.
This is nice, but everyone won't agree on using Debian as the base. It is developed by the right kind of organization for this and it's stable, but it's old. Like, Mozilla 1.0.0. Hello? Old GNOME and KDE as well.
Sure, I can use unstable, but that's not a good solution. Using another distribution that's based on a snapshot of Debian unstable could work, though. (I suppose it could be called UserLinux.)
Are dpkg installations interactive or does it just seem that way? I like that way rpm:s install without asking any questions and just give me a basic config file I can edit. Now that I have apt-rpm I'm pretty happy with my RPM-based distro. It's got recent, modern software, it's user-friendly and it works well. Why start over with Debian?
How does this relate to or even integrate with the new accessibility features in GNOME 2.4?
This is your fault. How does that make you feel?
There's KRB5/GSSAPI/IMAP support in Ximian Evolution nowadays. You need version 1.2.4 or later. It's enabled in the binaries for RHL9 from Ximian. A nice single-sign-on mail solution for sites with a Kerberos infrastructure.
For a moment there I thought it was a fan-made prequel to Galaxy Quest.
This would mean that there would be a database of all copyrighted works older than 50 years. In other words, if you have access to some potentially copyrighted work that you know is older than 50 years, you can simply look for it in the database. If it's not there, you're free to republish it!
Does that mean that Men are from Real, Women are from Microsoft?
What's next? A Kuro5hin text ad for your "massage therapy"?
Yeah, sure, the SIM card is just another way of authenticating to the network so you can log on and get you personal phone number. If you have some kind of secret code instead, that's fine. (Well, I suppose SIM cards are more secure, but I wouldn't know.)
The new owner of the phone should be able to put his own GSM-style SIM card with his own telephone number in the phone. By mapping telephone numbers to SIM cards instead of to telephones the buyer of a used phone don't have to worry about who the previous owner of the phone gave away his phone number to. (And as an added bonus he gets to keep is old number.)
A IDE RAID with a SCSI interface is a box with six or more slots for removable harddisks, six or more IDE interfaces, a CPU (or some other kind of microcontroller) running RAID software, a front panel (LCD and buttons), a serial port and a SCSI interface. The panel and serial port interfaces are used for things like setting the SCSI ID and telling the RAID controller what kind of RAID to use (0, 1, 5) and whether or not to use one of the disks as a standby spare disk (so that it can start rebuilding the RAID-5 set immediately if one disk fails.
All the computer sees is one gigantic SCSI disk. No special software or configuration is needed, even if the computer is booting from it.
There are RAID systems that make use of cheap IDE disks but still have a SCSI connection to computer. Until consumers wake up and start demanding that IDE and SCSI disks cost almost the same, I think this is an ideal solution. It works well and it's both fast and cheap.
I suppose it's possible to emulate most of this in IPv4 multicast using several streams, but it's not as automatic.
I think the basic problem is that 1.0.1 and 1.1 works so well that few people bothered to test the 1.2 alpha and beta. Hence serious bugs showing up in the release.
X works fine at a megabit per second or more and it works perfectly over IEEE802.11b.
No! The SunRays are really quite slow. Not at all much faster than running encrypted X over my DSL line at home to the server at work. X11 have some problems that make it less than optimal as a SunRay protocol, but it's not about speed, and it's nothing that couldn't be fixed, really. I'd say the reason has something to do with the "advantages" of a proprietary protocol.
Never overestimate the latency of a station wagon full of tapes following you everywhere you go, always within WaveLAN range. :-)
And if the kids are supposed to learn how to code, give them a well-designed language, instead of that awful crap called Matlab. Say, LISP. Or Perl! And BASH.
To write and distribute software, you get a computer, a fast internet connection and a website, all for around a thousand bucks a year. Since it's all so cheap, and you like coding, you just write stuff that benefits us all (everyone uses free software, whether they know it or not) and release it for free. Then you start to get nice letters from patent lawyers. Or you're selling your software, but you can't get a decent profit because all the big boys with lots of patents know how to use the system to make their competitors starve to death.
See? Patents in all areas, be it steam engines or audio compression algorithms, do both good and bad. They encourage innovation, but they also discourage the implementation of already existing ideas. With the above example I'd like to show that the negative effect of patents are a much larger factor in the software area than in other areas. It costs too much to get licenses, if they are at all for sale. The patents owners have too much power, beacause patents last for at least 20 years, in a fast-moving business that's only 50 years old. Software patents that expires after, say, two years would be OK.