I've heard that in many states, you can go to court again for non-payment, then the court can order the local sheriff to go with you to the defendant's property to start confiscating stuff for auction until the dept is paid. Although I don't know if this works for just businesses or individuals too.
Actually, Caldera bought some assetts from The Santa Cruz Operation (who renamed themselves to Trantella), then Caldera change their name to The SCO Group. But you are right about Caldera buying DR-DOS in order to inherit the law suit.
The problem of pointing to a company like Sendmail and using that as an example of success is like pointing to Madonna and saying that proves you can become mega-rich by singing a few songs. Not everyone who are really good singers (in fact very few) can make it big, and for the most part if you don't "make it big", you don't make it at all.
Same is true with open source software. There are really only two ways to make money from software in general... 1) exchange money for usage rights, or 2) use it as a loss leader to sell other products/services. With open source, (1) is out the window (with the exception of dual-licensing your code if your product is suitable for that, such as QT), and with (2) you are competing with everyone else who can also sell services based on your code, in addition to you having to invest in creating/maintaining your code (which your competitor doesn't have to do). Of course, you do have an advantage over your potential competitors by being the original author of the code (and owner of the trademarks, etc).
However, you do have the possibility to dual-license your code. What I would do is offer my code both under the GPL, and have the possibility for one to purchase a non-GPL license for, say, a couple million dollars. Then you'd be able to sue GPL violators for that large sum.
I've seen a fairly good plan put in place in some parts around here, where the power company can install a remote control for your A/C unit. The plan is that if they are running short on power they can selectively shut off air conditioners for a brief period of time. If you go along with this plan you get a slight discount from the power company, and a bigger discount if they have to enact this plan.
As for the "yucky" issue, the ones made by Lights of America seems fairly good. They have a different type of coating so that they appear more natural, not a harsh white output you get from the other ones. They also make a decent torchiere floor lamp that has 3 birghtness settings, each one seems to put out a slightly differnt color of light.
The thing I noticed (other than the wrong answers) was that a lot of the questions are aimed at a potentially different target. For example, why would you be asking a linux admin any dba-related questions? Also, the questions specific about various apache versions should be aimed at a web administrator (which falls under the applications group, not the sys-admin group, at least in a larger organization). I'd prefer to see a list of questions that pertain to the more non-technical aspects of system admin, such as proper change control procedures, importance of using well-tested and documented solutions, and reasons not to impliment something "just because you can". I may be getting cynical in my old age, but I've spent way too much time on cleaning up previous hot-shot admins' "handy work".
Re:Tivo has always been on my todo list
on
Can TiVo be Saved?
·
· Score: 1
Actually, I'm not buying a seperate box for MythTv. I, like many computer enthusiasts, tend to normally build my own boxes and upgrade components as they age. That leaves me with a few components lying around. So, I put together a server with a bunch of disk space to offload a bunch of my home "production" applications -- keep them off the box that I'm constantly playing with and onto something more stable. So, for an investment of $50 or so, I can add a basic capture card and have an instant dvr. Oh, and I also have the option to add additional tuners (currently waiting for some of the multi-tuner mpeg capture cards to be supported), and if I wanted to I can put together seperate front-end boxes for different TV's in the house (each front end can be used by a different family member, yet they all can pool the recordings on the main server). Again, these will be built from left-over components after various upgrades, and they will also be multi-purpose (I've been planning on putting computers in the kids' rooms anyways).
Well, there's a different way of looking at it. You see, I don't have a lot of time to just sit there and watch tv either. However, there are occasions in which I find myself with an hour or two of free time, and just need to "veg out". It used to be that I could flip on discovery channel, tlc, pbs, etc. and find something both entertaining and useful. But the content lately has been so watered down, that what is on 99% of the time I find nauseating. And the 1% of good content that is left out there isn't on when I have downtime. And I refuse to change my schedule around to fit the tv schedule. That is what a dvr is good for, making the most of the tv watching experience.
Now, those that already commit to 25 hours or more of tv viewing a week need to find something else, but if you only watch a couple of hours a week then a dvr can help keep those few hours from being totally wasted (i.e., you can make better use of the top 1% of content).
I think that would be implied by the requirement for a 16x pci express slot. As far as I'm aware, the only cards for these slots are video -- pci express raid & network cards do plenty with only a 1x pci express.
And those cases are now being thrown out, as the courts have ruled that this is illegal.
Re:Only if you don't do backups.
on
EFF's Logfinder
·
· Score: 2, Interesting
That's why you use a tape backup tool that has an "Enron/Anderson" mode. Before writing any file to tape, encrypt it with a random key and store that key in you file locator database. Then when it is time to expire a particular file version, all you have to do is delete the index record. No need to wipe the tape. This is useful if you have data on a tape that expires at different times. Also, for security, the random keys should then be passed through a public key encryption prior to being written to the database.
Just out of curiosity, do any of those anti-copying techniques prevent the image from being in the browsers cache? If not, then one could always pull up the most recent gif/jpegs from their cache directory.
But kids in the back seat screaming at each other tend to pay no attention to traffic situations. They'll just go on doing what they do to distract the driver.
Here's an example: A rear reflector isn't required on a bicycle, but if you do have one, then it _must_ be red. So having a "red rear reflector" on a bicycle is an optional standard.
A good item to add to this is this example: We are required to fill out an outage report and root cause analysis for each outage. So, if the kernel locks up for some reason (it happens from time to time, even on linux -- given a few hundred boxes of varying hardware quality...), and if there is no clear reason in the error log, stating "I don't know what happened, or why it happend, or how to prevent it in the future" just doesn't cut it. At least with vendor support, you can say "No log items produced, this incident has been turned over to the vendor for further investiagion, case number 1213459-X35B" That is what makes managers/customers happy.
If you already have a MythTV box set up (perferably with multiple tunners) then it would be nothing to set this up as a mythtv client. As for input, pick up a cheap $10 remote control, and use the mythtv plugin architecture to add your new apps, and bind the remote's keys to specific functions. This way, you've taken care of the tv, app, and input functionallity all in one shot.
One of the biggest things I've noticed is that it still takes a couple minutes to boot up a typical computer, and that applications take a few seconds to start, even though computers today are a thousand times faster than the ones 20 years ago.
Actually, the GPL only forces them to make sources available to thoes that they distribute the binaries to. Also, I don't believe there is any more proprietary code in RHEL. In version 2.1, I think there were a couple packages (IBM's java package for one) that weren't redistributable. But I think everything in 3.0 is. However, Redhat maintains a copyright on the cd layout (as a "collection"), which doesn't conflict with the GPL (since you are still free to redistribute any of the particular pieces of code). Also, they retain rights to their trademarks (logo's contained in the bitmaps, naming of the product, etc.). This is how they can get away with preventing you from distibuting iso images. But if you take all the source and re-compile and remove all the Redhat logo's, then you can distribute the result (you have to call it something other than Redhat Enterprise though). See Whitebox Enterprise Linux, Scientific Linux, Caos, Centos, etc...
When you're dealing with that much storage, you really need to catagorize your files into what needs to be backed up and what doesn't. In this type of application (if it was me), most of the storage is likely to be filled with dvd rips & mythtv recordings, or backups from your main system(s). So you would want to backup a list of what you have, but you can always recover from original media (in the case of dvd rips, or off of re-runs for tv shows). Also, on a storage server you're more likely to have data loss from physical driver failure (hence the raid 1 or 5), Since you won't be playing with the system that much once it's set up, you remove a lot of risk factors that you'd have on a desktop system (accidental file deletion, filesystem corruption,...)
I think the main reason for setting up a seperate box for your server is that you are less likely to "play around" with it. So your files are always available. You can tear down and rebuild your main box at will without the worry of loosing anything critical (keep you home directory nfs-mounted, etc.)
Also, you should never rely on autonegotiation -- there are no standards. That's what ethtool or mii-tool is for, or at a minimum specify speed/duplex in your/etc/modules.conf file.
In previous zaurus models this was a concern, since the most likely other use for the CF slot was for a microdrive. But with the built in drive, you most likely aren't going to need to put anything else in that slot, other than maybe a bluetooth adapter (which you probabably won't use at the same time as wifi), or a gps card (which you would want to use with wifi). However, the device does have a usb master port, so you can always use a usb wifi/storage/gps device. But then you've got portability issues...
The 5600 can more than double that if you can find one on ebay. The review says that the sl-c3000 lasted about 6 hours of article editing before getting a low-battery warning. My experience with my new zaurus 6000 unit seems to confirm this. However, using the wireless card will cut battery life in half -- or it used to on mine -- I've since adapted the diald program to automatically turn on & off the wireless card after 15 seconds of inactivity, which brings the battery life back up to normal. Also, it all depends on how bright you make the display. I'm not sure about the c3000, but on the 6000 if I have the brightness set up all the way it hurts my eyes. I have to turn it down a couple of notches, unless I'm outdoors. Even then, the backlight is only needed if your in the shade (i.e., a lot of ambient light), but in direct sunlight the screen seems to be quiet readable.
Slashdot Mirror
I've heard that in many states, you can go to court again for non-payment, then the court can order the local sheriff to go with you to the defendant's property to start confiscating stuff for auction until the dept is paid. Although I don't know if this works for just businesses or individuals too.
Actually, Caldera bought some assetts from The Santa Cruz Operation (who renamed themselves to Trantella), then Caldera change their name to The SCO Group. But you are right about Caldera buying DR-DOS in order to inherit the law suit.
Same is true with open source software. There are really only two ways to make money from software in general... 1) exchange money for usage rights, or 2) use it as a loss leader to sell other products/services. With open source, (1) is out the window (with the exception of dual-licensing your code if your product is suitable for that, such as QT), and with (2) you are competing with everyone else who can also sell services based on your code, in addition to you having to invest in creating/maintaining your code (which your competitor doesn't have to do). Of course, you do have an advantage over your potential competitors by being the original author of the code (and owner of the trademarks, etc).
However, you do have the possibility to dual-license your code. What I would do is offer my code both under the GPL, and have the possibility for one to purchase a non-GPL license for, say, a couple million dollars. Then you'd be able to sue GPL violators for that large sum.
I've seen a fairly good plan put in place in some parts around here, where the power company can install a remote control for your A/C unit. The plan is that if they are running short on power they can selectively shut off air conditioners for a brief period of time. If you go along with this plan you get a slight discount from the power company, and a bigger discount if they have to enact this plan.
As for the "yucky" issue, the ones made by Lights of America seems fairly good. They have a different type of coating so that they appear more natural, not a harsh white output you get from the other ones. They also make a decent torchiere floor lamp that has 3 birghtness settings, each one seems to put out a slightly differnt color of light.
The thing I noticed (other than the wrong answers) was that a lot of the questions are aimed at a potentially different target. For example, why would you be asking a linux admin any dba-related questions? Also, the questions specific about various apache versions should be aimed at a web administrator (which falls under the applications group, not the sys-admin group, at least in a larger organization).
I'd prefer to see a list of questions that pertain to the more non-technical aspects of system admin, such as proper change control procedures, importance of using well-tested and documented solutions, and reasons not to impliment something "just because you can". I may be getting cynical in my old age, but I've spent way too much time on cleaning up previous hot-shot admins' "handy work".
Actually, I'm not buying a seperate box for MythTv. I, like many computer enthusiasts, tend to normally build my own boxes and upgrade components as they age. That leaves me with a few components lying around. So, I put together a server with a bunch of disk space to offload a bunch of my home "production" applications -- keep them off the box that I'm constantly playing with and onto something more stable.
So, for an investment of $50 or so, I can add a basic capture card and have an instant dvr. Oh, and I also have the option to add additional tuners (currently waiting for some of the multi-tuner mpeg capture cards to be supported), and if I wanted to I can put together seperate front-end boxes for different TV's in the house (each front end can be used by a different family member, yet they all can pool the recordings on the main server). Again, these will be built from left-over components after various upgrades, and they will also be multi-purpose (I've been planning on putting computers in the kids' rooms anyways).
Well, there's a different way of looking at it. You see, I don't have a lot of time to just sit there and watch tv either. However, there are occasions in which I find myself with an hour or two of free time, and just need to "veg out". It used to be that I could flip on discovery channel, tlc, pbs, etc. and find something both entertaining and useful. But the content lately has been so watered down, that what is on 99% of the time I find nauseating. And the 1% of good content that is left out there isn't on when I have downtime. And I refuse to change my schedule around to fit the tv schedule. That is what a dvr is good for, making the most of the tv watching experience.
Now, those that already commit to 25 hours or more of tv viewing a week need to find something else, but if you only watch a couple of hours a week then a dvr can help keep those few hours from being totally wasted (i.e., you can make better use of the top 1% of content).
I think that would be implied by the requirement for a 16x pci express slot. As far as I'm aware, the only cards for these slots are video -- pci express raid & network cards do plenty with only a 1x pci express.
And those cases are now being thrown out, as the courts have ruled that this is illegal.
That's why you use a tape backup tool that has an "Enron/Anderson" mode. Before writing any file to tape, encrypt it with a random key and store that key in you file locator database. Then when it is time to expire a particular file version, all you have to do is delete the index record. No need to wipe the tape. This is useful if you have data on a tape that expires at different times.
Also, for security, the random keys should then be passed through a public key encryption prior to being written to the database.
Just out of curiosity, do any of those anti-copying techniques prevent the image from being in the browsers cache? If not, then one could always pull up the most recent gif/jpegs from their cache directory.
But kids in the back seat screaming at each other tend to pay no attention to traffic situations. They'll just go on doing what they do to distract the driver.
Here's an example:
A rear reflector isn't required on a bicycle, but if you do have one, then it _must_ be red. So having a "red rear reflector" on a bicycle is an optional standard.
A good item to add to this is this example:
We are required to fill out an outage report and root cause analysis for each outage. So, if the kernel locks up for some reason (it happens from time to time, even on linux -- given a few hundred boxes of varying hardware quality...), and if there is no clear reason in the error log, stating "I don't know what happened, or why it happend, or how to prevent it in the future" just doesn't cut it. At least with vendor support, you can say "No log items produced, this incident has been turned over to the vendor for further investiagion, case number 1213459-X35B"
That is what makes managers/customers happy.
If you already have a MythTV box set up (perferably with multiple tunners) then it would be nothing to set this up as a mythtv client. As for input, pick up a cheap $10 remote control, and use the mythtv plugin architecture to add your new apps, and bind the remote's keys to specific functions.
This way, you've taken care of the tv, app, and input functionallity all in one shot.
One of the biggest things I've noticed is that it still takes a couple minutes to boot up a typical computer, and that applications take a few seconds to start, even though computers today are a thousand times faster than the ones 20 years ago.
But don't you know that you can wipe out the RFID by putting the tinfoil in the microwave?
Actually, the GPL only forces them to make sources available to thoes that they distribute the binaries to.
Also, I don't believe there is any more proprietary code in RHEL. In version 2.1, I think there were a couple packages (IBM's java package for one) that weren't redistributable. But I think everything in 3.0 is.
However, Redhat maintains a copyright on the cd layout (as a "collection"), which doesn't conflict with the GPL (since you are still free to redistribute any of the particular pieces of code).
Also, they retain rights to their trademarks (logo's contained in the bitmaps, naming of the product, etc.). This is how they can get away with preventing you from distibuting iso images. But if you take all the source and re-compile and remove all the Redhat logo's, then you can distribute the result (you have to call it something other than Redhat Enterprise though). See Whitebox Enterprise Linux, Scientific Linux, Caos, Centos, etc...
When you're dealing with that much storage, you really need to catagorize your files into what needs to be backed up and what doesn't. In this type of application (if it was me), most of the storage is likely to be filled with dvd rips & mythtv recordings, or backups from your main system(s). So you would want to backup a list of what you have, but you can always recover from original media (in the case of dvd rips, or off of re-runs for tv shows). Also, on a storage server you're more likely to have data loss from physical driver failure (hence the raid 1 or 5), Since you won't be playing with the system that much once it's set up, you remove a lot of risk factors that you'd have on a desktop system (accidental file deletion, filesystem corruption, ...)
I think the main reason for setting up a seperate box for your server is that you are less likely to "play around" with it. So your files are always available. You can tear down and rebuild your main box at will without the worry of loosing anything critical (keep you home directory nfs-mounted, etc.)
Also, you should never rely on autonegotiation -- there are no standards. That's what ethtool or mii-tool is for, or at a minimum specify speed/duplex in your /etc/modules.conf file.
In previous zaurus models this was a concern, since the most likely other use for the CF slot was for a microdrive. But with the built in drive, you most likely aren't going to need to put anything else in that slot, other than maybe a bluetooth adapter (which you probabably won't use at the same time as wifi), or a gps card (which you would want to use with wifi). However, the device does have a usb master port, so you can always use a usb wifi/storage/gps device. But then you've got portability issues...
The 5600 can more than double that if you can find one on ebay. The review says that the sl-c3000 lasted about 6 hours of article editing before getting a low-battery warning. My experience with my new zaurus 6000 unit seems to confirm this. However, using the wireless card will cut battery life in half -- or it used to on mine -- I've since adapted the diald program to automatically turn on & off the wireless card after 15 seconds of inactivity, which brings the battery life back up to normal.
Also, it all depends on how bright you make the display. I'm not sure about the c3000, but on the 6000 if I have the brightness set up all the way it hurts my eyes. I have to turn it down a couple of notches, unless I'm outdoors. Even then, the backlight is only needed if your in the shade (i.e., a lot of ambient light), but in direct sunlight the screen seems to be quiet readable.