Why not offer some radio services for free - with advertisements - and premium commercial-free versions for those that'd like to pay.
This would allow advertising to flow into people's ears even if they weren't paying for service, but still had a in-dash receiver.
Not to say I want advertising, but if I ever decide to cancel my subscription that's only usable on a $400 radio, I'd like to be able to use it for _something_.
It wouldn't cost them any _more_ to broadcast a few non-subscription streams (except perhaps for a few paid "channels") and it might get some people who have the units, but have either not yet subscribed, or canceled their subscription, to sign up (again).
Perhaps they could offer a function by which you could turn a song you just finished listening to into an MP3 which you could listen to later.
I'm not sure how they could charge for this service considering it's a one-way communication link.....
But having an in-car MP3 recorder always recording with a back buffer of 5 minutes or so could come in handy for adding to that MP3 collection of your s the song you just heard!
An Identity Base Encryption (IBE) scheme is a public-key cryptosystem where any string is a valid public key. In particular, email addresses are public keys. Only a trusted party knows the private key corresponding to a particular public key.
In standard public-key cryptosystems such as RSA, if Alice wants to send Bob an encrypted message, Bob must first generate a public key, and then Alice must retrieve it before she can encrypt. Alternatively, there might exist a directory service; a third party generates a public key on Bob's behalf (and gives the private key to Bob later), but Alice must still retrieve this key from this directory service.
With IBE, if Alice wants to send Bob an encrypted message, she simply encrypts using Bob's email address. Thus Bob's email address is his public key; there is no need for Bob to use cryptography software to generate a public key, nor does Alice have to retrieve a public key from Bob, or from a directory service.
Once Bob receives an encrypted message, he retrieves his private key from the trusted server (he only has to do this the first time) and then decrypts.
The main aim of this project to encourage use of encrypted email. Conventional public-key systems have trouble spreading beecause the average user has little motivation to generate keys. However, because the trusted server (or servers) knows every user's private key (i.e. the system has built-in key escrow), it is hoped that users will migrate to traditional public-key cryptosystems, and we are ressearching how to automate the transition and make it as seamless as possible. (For example, since the server is trusted, it naturally takes on the role of a certificate authority when switching to standard cryptosystems.)
Get your own private key here or download the GPLed source or windows binaries here.
I've been working as a student systems administrator for a computer lab at Cornell for the last 3 years on linux and NT systems. We've got lots of students with root access to some machines quite critical to the operation of the lab. We have had, on many occasions, situations where a lack of communication and multiple people working on the same project/server/whathaveyou, shall I say, stepped on eachother's toes. I'm not sure if we ever implemented any of these, but I've done some thinking about it! (especially after a day's worth of work on a config file gets blown away by a vi edit from another guy with root who doesn't know what he's doing....) Anyway, here's a few things you could do...
1) Set up a cron job to backup configuration files You could either write a simple script to tar up/etc/* or whatever other files your clients might want to fowl up. Or you could use the logrotate program. It's a flexible solution to manage log files and could be used to tar up and compress periodically the files you'd like to backup should anything get messed up.
2) Use the "wheel" group to allow only certain users to perform administrative functions on files you chown root.wheel. You could also do this for a "web" group (#chgrp -R web/home/www) or anything else to give access to certain files for certain people. Instead of "giving them root," ask them which users want to have control over which sets of specific files on the system, make groups for each set of files, and add the users to the group that need access. This would allow you to track down more easily who modified a certain file, since only a few people may have had access to it. (easier finger pointing basically). This is much better than knowing that a bunch of people could have done it, and getting blamed for it yourself.
3) Setup sudo Edit/etc/sudoers
4) Use process accounting
5) Set up a simple kerberos5 installation This allows you to give root [or any other administrative-type account function] access to certain users via a ".k5login" file. This allows you [root] to simply add users who are allowed root access [to kerberized services] by putting their principal [system user account name] in root's.k5login file. You needn't give them the root password. They can just login as themselves and they will be allowed to use their own tickets to access kerberized services that require a "root" principal. All access is logged so that backtracing who did what and when would be possible. Note: This may be an unnecessarially complex method to implement. It can however be used for a wide variety of services and is considered quite secure and flexible, particularly for large networks. It won't work for general file access, but if you can kerberize some of the services you'd like to administer, this would help immensely.
6) Tell them to make backups before they change anything or implement a CVS system on all config files that anyone would want to changeCVSing config files would force documentation and allow you to revert to any previous incarnation of your system if something somehow "broke."
Sullivan manages to undermine her argument by suggesting that someone can always use a video camera to tape a copy of a DVD being played on approved equipment...
I think the point is that the fair use is lost because you must use a player that is restricted by "Regions," etc. and cannot utilize the material that you purchased without first decrypting the content.
Why should a person have to go out and purchase a regluated playback device to view the content they bought in the first place? It's my DVD and I want to watch the movie on it, but I have to PAY a "licensed DVD playback manufacturer" to watch the ENCRYPTED video????????? That's absurd!
DeCSS is just providing me that key to unlock what is rightfully mine. One of those "licensed DVD playback manufacturers" screwed up and let the cat out of the bag. What is so illegal about unlocking what is rightfully mine? This "fair use" is like going to the grocery store to buy a box of cereal and getting it home to find the box locked. Now I need to go back to the grocery store and buy a key to eat my cereal???
Anyway, the 2600 lawyer started heading down the wrong road talking about how a person can video record the playback from a DVD player. The point is that we shouldn't have to go out to BUY a player that has some secret code in it (yes. you ARE paying for the secret codes....) just to utilize the material we purchased in the DVD format. The material is MINE. It is only fair to me to have access to it without having to spend more money. While true that if I buy a pre-recorded VHS casette, I need a VHS playback device to view the material. But I DON'T need to buy it from someone who spent a lot of money to license a secret code that allows me to play it. I can build a VHS VCR if I want and play back my pre-recorded video. While difficult, it's possible and legally kosher. The DVD is a whole different story because what's mine isn't mine until I pay someone else to use it........
Distros and their package managers need to somehow find a way to hide all the distro-specific features and script-dependent software install settings behind some form of abstraction layer.
Rather than a "Red Hat RPM" or a "SuSE RPM" we could just have "RPMs" that would abstract all the details. The specifics on file placement that are inherent to the current situation [above] and to the package files themselves must be standardized and abstracted before linux will get that support and enthusiasm from both commercial software vendors and endusers alike. Same goes for APT and tgz (as well as other package types) as well.
This kind of thing is really great and all, but it also makes me a bit nervous.......
I get anxious when control is taken away from the user. I really hate when products produced these days are "dumbed
down" to make them useable by idiots and any level of control is destroyed.
Let the servers heal themselves, just don't make it any MORE difficult for an IT person to manage the machine just
because it thinks it's smarter than the administrator trying to run the thing!
Ummm...like Macintoshes? I hate being greeted by a frowning Mr. Mac - wouldn't an error message be more
useful? Of course - but then you wouldn't want the user to try and fix anything, would you?
Exactly!!!!
What if I really do CARE how many colors there are? Hundreds of colors, thousands of colors, millions of colors????? What am I, an idiot?! Options like these make me feel like I'm not supposed to know where the power switch is or why the iMac comes with a slide out cup holder.
These little things kinda piss me off. Maybe I want to know a small piece of information that could EASILY be integrated into the user interface? Why hide it? Mac's just bug me for reasons like this.
This attitude is very typical of many of todays consumer electronics devices. It's like they were designed by Fisher-Price! To make the device useable by any mentally challenged 2nd grader, today's manufacturers systematically eliminate any level of control. They reduce all the complexity and potential for control into a single button. "Smart" devices aren't really that smart. They are just preprogrammed by some technician at the factory to behave like that person thinks you are going to want it to behave. Why not give the user the option to change, but at the same time - provide the stupid user a button that will "do everything for you." Like the flip up lids on lots of remote controls for really fancy TVs. I think thats Great! Hide the complexity, fine, but don't take it away......... Geesh.
I'm just ranting incase there are any designers out there. I think it's fine to make things useable by idiots, but taking the flexibility away from lots of devices today that have huge potential for flexibility and control is wrong. By giving point and shoot cameras only an "AUTO" button is teaching society to just accept the exposure mode set at the factory. We are taking away from society the ability to be creative - the ability to get our hands, thoughts and ideas into today's modern pieces of technological wonder.
People today love talking about how kids are so smart and "good with computers." The trick is, that 9 times out of 10, they click the mouse button on the right part of the screen (ohhhh... ahhhh.... eye-hand coordination) and out comes something that their parents can show off to grandma. Well, guess what Mom? Billy isn't that smart. All the "smarts" are built in!
What if Billy wants to change the size of the picture? Nope. Can't do it with this wonderful piece of crap preinstalled software that came with your pice of shit Compaq from RadioSmack. ["You've got questions. We've got blank stares."] What if Billy wants to put in his report some numbers, each with parentheses after them? 1) 25) ??? Well he's going to have a hell of a time trying to convice Microsoft's wonderful Word2000 to let him do that by himself.......
You all know what I'm talking about. I'm all about giving the idiots of this world an "AUTO" button, but at least provide the people who want to make adjustments the ability to do so! You stifle my creativity. You make me look like everybody else. You standardize me and patronize. You condescend me you evil "AUTO"-button......
This kind of thing is really great and all, but it also makes me a bit nervous.......
I get anxious when control is taken away from the user. I really hate when products produced these days are "dumbed down" to make them useable by idiots and any level of control is destroyed.
Let the servers heal themselves, just don't make it any MORE difficult for an IT person to manage the machine just because it thinks it's smarter than the administrator trying to run the thing!
For the latter, color is nothing but the interpretation of a wavelength. Creating colors on your monitor is really just controlling the interference between the light waves.
Color has nothing to do with the "interference" between the light waves. Your eyes can intercept two wavelengths and they appear to be of another. This is due to our eye interpreting the simultaneous stimulation of two wavelengths as another color. It has nothing to do with the two wavelengths "interfering" in the traditional sense.
http://www.linuxdevices.com/files/eprom/eprom.html For cooling, use natural convection as much as you can by standing the machine upright (on it's side rather than horizontal.) Then make sure the cards at 90 deg to the board are vertical so air can easily pass by them. Also be sure to use lots of extended surfaces (fins - heat sinks......). This is a good start if you can't use fans. Good luck.
Slashdot Mirror
Why not offer some radio services for free - with advertisements - and premium commercial-free versions for those that'd like to pay.
This would allow advertising to flow into people's ears even if they weren't paying for service, but still had a in-dash receiver.
Not to say I want advertising, but if I ever decide to cancel my subscription that's only usable on a $400 radio, I'd like to be able to use it for _something_.
It wouldn't cost them any _more_ to broadcast a few non-subscription streams (except perhaps for a few paid "channels") and it might get some people who have the units, but have either not yet subscribed, or canceled their subscription, to sign up (again).
With in-car MP3
.....
Perhaps they could offer a function by which you could turn a song you just finished listening to into an MP3 which you could listen to later.
I'm not sure how they could charge for this service considering it's a one-way communication link
But having an in-car MP3 recorder always recording with a back buffer of 5 minutes or so could come in handy for adding to that MP3 collection of your s the song you just heard!
I love hybridizing technologies!
http://crypto.stanford.edu/ibe/
Based on ellipses.
An Identity Base Encryption (IBE) scheme is a public-key cryptosystem where any string is a valid public key. In particular, email addresses are public keys. Only a trusted party knows the private key corresponding to a particular public key.
In standard public-key cryptosystems such as RSA, if Alice wants to send Bob an encrypted message, Bob must first generate a public key, and then Alice must retrieve it before she can encrypt. Alternatively, there might exist a directory service; a third party generates a public key on Bob's behalf (and gives the private key to Bob later), but Alice must still retrieve this key from this directory service.
With IBE, if Alice wants to send Bob an encrypted message, she simply encrypts using Bob's email address. Thus Bob's email address is his public key; there is no need for Bob to use cryptography software to generate a public key, nor does Alice have to retrieve a public key from Bob, or from a directory service.
Once Bob receives an encrypted message, he retrieves his private key from the trusted server (he only has to do this the first time) and then decrypts.
The main aim of this project to encourage use of encrypted email. Conventional public-key systems have trouble spreading beecause the average user has little motivation to generate keys. However, because the trusted server (or servers) knows every user's private key (i.e. the system has built-in key escrow), it is hoped that users will migrate to traditional public-key cryptosystems, and we are ressearching how to automate the transition and make it as seamless as possible. (For example, since the server is trusted, it naturally takes on the role of a certificate authority when switching to standard cryptosystems.)
Get your own private key here or download the GPLed source or windows binaries here.
I've been working as a student systems administrator for a computer lab at Cornell for the last 3 years on linux and NT systems. We've got lots of students with root access to some machines quite critical to the operation of the lab. We have had, on many occasions, situations where a lack of communication and multiple people working on the same project/server/whathaveyou, shall I say, stepped on eachother's toes. I'm not sure if we ever implemented any of these, but I've done some thinking about it! (especially after a day's worth of work on a config file gets blown away by a vi edit from another guy with root who doesn't know what he's doing....) Anyway, here's a few things you could do...
1) Set up a cron job to backup configuration files
You could either write a simple script to tar up
2) Use the "wheel" group
to allow only certain users to perform administrative functions on files you chown root.wheel. You could also do this for a "web" group (#chgrp -R web
3) Setup sudo
Edit
4) Use process accounting
5) Set up a simple kerberos5 installation
This allows you to give root [or any other administrative-type account function] access to certain users via a ".k5login" file. This allows you [root] to simply add users who are allowed root access [to kerberized services] by putting their principal [system user account name] in root's
6) Tell them to make backups before they change anything or implement a CVS system
on all config files that anyone would want to changeCVSing config files would force documentation and allow you to revert to any previous incarnation of your system if something somehow "broke."
Hope this helps!
May I just say: "so what?"
Not news for nerds.
Sullivan manages to undermine her argument by suggesting that someone can always use a video camera to tape a copy of a DVD being played on approved equipment...
I think the point is that the fair use is lost because you must use a player that is restricted by "Regions," etc. and cannot utilize the material that you purchased without first decrypting the content.
Why should a person have to go out and purchase a regluated playback device to view the content they bought in the first place? It's my DVD and I want to watch the movie on it, but I have to PAY a "licensed DVD playback manufacturer" to watch the ENCRYPTED video????????? That's absurd!
DeCSS is just providing me that key to unlock what is rightfully mine. One of those "licensed DVD playback manufacturers" screwed up and let the cat out of the bag. What is so illegal about unlocking what is rightfully mine? This "fair use" is like going to the grocery store to buy a box of cereal and getting it home to find the box locked. Now I need to go back to the grocery store and buy a key to eat my cereal???
Anyway, the 2600 lawyer started heading down the wrong road talking about how a person can video record the playback from a DVD player. The point is that we shouldn't have to go out to BUY a player that has some secret code in it (yes. you ARE paying for the secret codes....) just to utilize the material we purchased in the DVD format. The material is MINE. It is only fair to me to have access to it without having to spend more money. While true that if I buy a pre-recorded VHS casette, I need a VHS playback device to view the material. But I DON'T need to buy it from someone who spent a lot of money to license a secret code that allows me to play it. I can build a VHS VCR if I want and play back my pre-recorded video. While difficult, it's possible and legally kosher. The DVD is a whole different story because what's mine isn't mine until I pay someone else to use it........
Distros and their package managers need to somehow find a way to hide all the distro-specific features and script-dependent software install settings behind some form of abstraction layer.
Rather than a "Red Hat RPM" or a "SuSE RPM" we could just have "RPMs" that would abstract all the details. The specifics on file placement that are inherent to the current situation [above] and to the package files themselves must be standardized and abstracted before linux will get that support and enthusiasm from both commercial software vendors and endusers alike. Same goes for APT and tgz (as well as other package types) as well.
This kind of thing is really great and all, but it also makes me a bit nervous.......
I get anxious when control is taken away from the user. I really hate when products produced these days are "dumbed down" to make them useable by idiots and any level of control is destroyed.
Let the servers heal themselves, just don't make it any MORE difficult for an IT person to manage the machine just because it thinks it's smarter than the administrator trying to run the thing!
Ummm...like Macintoshes? I hate being greeted by a frowning Mr. Mac - wouldn't an error message be more useful? Of course - but then you wouldn't want the user to try and fix anything, would you?
Exactly!!!!
What if I really do CARE how many colors there are? Hundreds of colors, thousands of colors, millions of colors????? What am I, an idiot?! Options like these make me feel like I'm not supposed to know where the power switch is or why the iMac comes with a slide out cup holder.
These little things kinda piss me off. Maybe I want to know a small piece of information that could EASILY be integrated into the user interface? Why hide it? Mac's just bug me for reasons like this.
This attitude is very typical of many of todays consumer electronics devices. It's like they were designed by Fisher-Price! To make the device useable by any mentally challenged 2nd grader, today's manufacturers systematically eliminate any level of control. They reduce all the complexity and potential for control into a single button. "Smart" devices aren't really that smart. They are just preprogrammed by some technician at the factory to behave like that person thinks you are going to want it to behave. Why not give the user the option to change, but at the same time - provide the stupid user a button that will "do everything for you." Like the flip up lids on lots of remote controls for really fancy TVs. I think thats Great! Hide the complexity, fine, but don't take it away......... Geesh.
I'm just ranting incase there are any designers out there. I think it's fine to make things useable by idiots, but taking the flexibility away from lots of devices today that have huge potential for flexibility and control is wrong. By giving point and shoot cameras only an "AUTO" button is teaching society to just accept the exposure mode set at the factory. We are taking away from society the ability to be creative - the ability to get our hands, thoughts and ideas into today's modern pieces of technological wonder.
People today love talking about how kids are so smart and "good with computers." The trick is, that 9 times out of 10, they click the mouse button on the right part of the screen (ohhhh... ahhhh.... eye-hand coordination) and out comes something that their parents can show off to grandma. Well, guess what Mom? Billy isn't that smart. All the "smarts" are built in!
What if Billy wants to change the size of the picture? Nope. Can't do it with this wonderful piece of crap preinstalled software that came with your pice of shit Compaq from RadioSmack. ["You've got questions. We've got blank stares."] What if Billy wants to put in his report some numbers, each with parentheses after them? 1) 25) ??? Well he's going to have a hell of a time trying to convice Microsoft's wonderful Word2000 to let him do that by himself.......
You all know what I'm talking about. I'm all about giving the idiots of this world an "AUTO" button, but at least provide the people who want to make adjustments the ability to do so! You stifle my creativity. You make me look like everybody else. You standardize me and patronize. You condescend me you evil "AUTO"-button......
This kind of thing is really great and all, but it also makes me a bit nervous.......
I get anxious when control is taken away from the user. I really hate when products produced these days are "dumbed down" to make them useable by idiots and any level of control is destroyed.
Let the servers heal themselves, just don't make it any MORE difficult for an IT person to manage the machine just because it thinks it's smarter than the administrator trying to run the thing!
http://www.isso.uh.edu/publications/A9900/html/mi
For the latter, color is nothing but the interpretation of a wavelength. Creating colors on your monitor is really just controlling the interference between the light waves.
Color has nothing to do with the "interference" between the light waves. Your eyes can intercept two wavelengths and they appear to be of another. This is due to our eye interpreting the simultaneous stimulation of two wavelengths as another color. It has nothing to do with the two wavelengths "interfering" in the traditional sense.
If anyone gets something like this working, it'd be interesting to see some practical plans put up on the web!
Anybody know where one might procure some appropritate X-ray sensitive film to use with this device? Exposure?
Way to go nebby!
Cornell Student Linux Users Group @ http://cslug.cornell.edu
I finished 3 versions of the maze in less than a minute. 4 dimensions are easier than 2!
http://www.linuxdevices.com/files/eprom/eprom.html
For cooling, use natural convection as much as you can by standing the machine upright (on it's side rather than horizontal.) Then make sure the cards at 90 deg to the board are vertical so air can easily pass by them. Also be sure to use lots of extended surfaces (fins - heat sinks......). This is a good start if you can't use fans.
Good luck.