HyperSCSI is a networking protocol designed for the transmission of SCSI commands and data across a network. To put this in "ordinary" terms, it can allow one to connect to and use SCSI and SCSI-based devices (like IDE, USB, Fibre Channel) over a network as if it was directly attached locally.
What would happen if you combined the temp fail implementation with a subscription token sent transparantly from the smtp server. If there is a real person on the other side, the token is quickly replied so communication can occur. If you would then give this token a certain cost (number of bytes), depending on maybe domain name or spammyness of the sendername, wouldn't it be possible to avoid spam at the cost of a 'handshake' mail?
"Remember that a desktop user does NOT WANT to understand his computer." "Linux just doesn't get it when it comes to dumb-ass desktop users"
First of all, most dumb-ass users you describe are Windows users, who are desperately looking for a 'config-your-sound/video/...-card-here' icon, which is not what a user is supposed to be doing. (ie once they see me doing stuff in console as root to config it, they seem to perfectly understand the difference between user and superuser-space).
These people are used to MS applications (and thus will take things like abiword for granted), and they usually just want to know what new 'options' this new os will provide for their sound/video/...-card.
My point being: A user is someone who _works_ on a computer. (ie someone interested in the _programs_ he or she works with)
Second, when a user (as described above) is working, he or she _does_ want to know what is happening. But their afraid to ask, because windows admins tend to cover their mistakes with bullshit explenations, and if they're accepted as possible cause of the problem, these admins will keep telling you bullshit you don't understand. This works both ways ofcourse, an admin with an easy job and a user who shuts the hell up....
Have you ever supported windows users on their linux server? (ie login, service adsl restart, logout) Once these people realize this kind of support is something that allways works, they will get curious and ask about other command lines, because this is a simpel concept, you type something and it works, or it complains.
The reason I'm saying this, is because I support a customer who uses a linux server and windows clients. This customer is willing to switch to linux, because support for it is possible through voice telephone (this sounds odd, but think about it, you should only know how to open a console, and how to type. A windows user need to know _where_ to click, and how will he tell you it worked? `echo $?` ?:)
Re:Luke, use the source...
on
Is RPM Doomed?
·
· Score: 3, Informative
> I administer a few RedHat servers...
Once you administer 20+ of 'em with other admins, you are going to need a package management system.
Slashdot Mirror
from the website:
HyperSCSI is a networking protocol designed for the transmission of SCSI commands and data across a network. To put this in "ordinary" terms, it can allow one to connect to and use SCSI and SCSI-based devices (like IDE, USB, Fibre Channel) over a network as if it was directly attached locally.
http://nst.dsi.a-star.edu.sg/mcsa/hyperscsi/
What would happen if you combined the temp fail implementation with a subscription token sent transparantly from the smtp server. If there is a real person on the other side, the token is quickly replied so communication can occur. If you would then give this token a certain cost (number of bytes), depending on maybe domain name or spammyness of the sendername, wouldn't it be possible to avoid spam at the cost of a 'handshake' mail?
It might hurt your eyes but it is well designed
in opera, try: view -> style -> usermode
I presume most browsers have similar features...
"Linux just doesn't get it when it comes to dumb-ass desktop users"
First of all, most dumb-ass users you describe are Windows users, who are desperately looking for a 'config-your-sound/video/...-card-here' icon, which is not what a user is supposed to be doing. (ie once they see me doing stuff in console as root to config it, they seem to perfectly understand the difference between user and superuser-space).
These people are used to MS applications (and thus will take things like abiword for granted), and they usually just want to know what new 'options' this new os will provide for their sound/video/...-card.
My point being: A user is someone who _works_ on a computer. (ie someone interested in the _programs_ he or she works with)
Second, when a user (as described above) is working, he or she _does_ want to know what is happening. But their afraid to ask, because windows admins tend to cover their mistakes with bullshit explenations, and if they're accepted as possible cause of the problem, these admins will keep telling you bullshit you don't understand. This works both ways ofcourse, an admin with an easy job and a user who shuts the hell up....
Have you ever supported windows users on their linux server? (ie login, service adsl restart, logout) Once these people realize this kind of support is something that allways works, they will get curious and ask about other command lines, because this is a simpel concept, you type something and it works, or it complains.
The reason I'm saying this, is because I support a customer who uses a linux server and windows clients. This customer is willing to switch to linux, because support for it is possible through voice telephone (this sounds odd, but think about it, you should only know how to open a console, and how to type. A windows user need to know _where_ to click, and how will he tell you it worked? `echo $?` ?
> I administer a few RedHat servers...
:)
Once you administer 20+ of 'em with other admins, you are going to need a package management system.
Unless you think keeping notes really works
---
blaze-x