Yes. Fayetteville State University in North Carolina had one. I don't know if they still do. It had about 20 terminals hooked up to it in one room and had dialup access as well. Nor do I remember how many processors it had, but it ran well enough for what it had to do (education).
Now that's scary. Having to run an SMP machine to be able to use Micro$oft's latest OS. I can see the minimum hardware requirements on the side of the box now. Four Pentium Pro 5 processors, 1 Gigabyte of shared RAM, and 2 Gigabytes of free hard disk space. (For optional voice interface add another Gigabyte of both memory and hard disk space.)
I have a graphical tar client that runs on Windows 95. Part of the Exceed package from Hummingbird. Having a tape deck connected to the linux machine I wanted to use it to back up files from the Windows 95 machine. I created a link from the tape device into a Samba share and simply named it tape. Now a file appears on the Windows 95 box named tape. The tar client reads it and writes it and the tape deck turns. Way cool! Now, could you do that with NT?
Another place where I think it would serve a useful purpose is in maintaining the local cache for the AFS cache manager. The CODA file system has a similar process, but I don't remember if it's called a cache manager or not. Also, and this is really repeating what a couple of people have already said, if a job is IO bound, then actually using it for a filesystem would not be unreasonable. Like all things, an engineering decision would need to be made on the cost/benifit ratio. I do think they are cool, but last time I saw prices I shuddered!
When was the last time any of you were in a police cruiser? Or a utilities vehicle. They have mobile computing figured out. You may not like the way they do it however. Most have laptops mounted on a special rig so that it can be accessed from the drivers position. Depending upon the size of your vehicle this could interfere with the passenger. Otherwise its probably the best thing going.
Slashdot Mirror
Yes. Fayetteville State University in North Carolina had one. I don't know if they still do. It had about 20 terminals hooked up to it in one room and had dialup access as well. Nor do I remember how many processors it had, but it ran well enough for what it had to do (education).
Now that's scary. Having to run an SMP machine to be able to use Micro$oft's latest OS. I can see the minimum hardware requirements on the side of the box now. Four Pentium Pro 5 processors, 1 Gigabyte of shared RAM, and 2 Gigabytes of free hard disk space. (For optional voice interface add another Gigabyte of both memory and hard disk space.)
I have a graphical tar client that runs on Windows 95. Part of the Exceed package from Hummingbird. Having a tape deck connected to the linux machine I wanted to use it to back up files from the Windows 95 machine. I created a link from the tape device into a Samba share and simply named it tape. Now a file appears on the Windows 95 box named tape. The tar client reads it and writes it and the tape deck turns. Way cool! Now, could you do that with NT?
Another place where I think it would serve a useful purpose is in maintaining the local cache for the AFS cache manager. The CODA file system
has a similar process, but I don't remember if
it's called a cache manager or not. Also, and
this is really repeating what a couple of people
have already said, if a job is IO bound, then
actually using it for a filesystem would not be
unreasonable. Like all things, an engineering
decision would need to be made on the cost/benifit
ratio. I do think they are cool, but last time
I saw prices I shuddered!
When was the last time any of you were in a police cruiser? Or a utilities vehicle. They have mobile
computing figured out. You may not like the way they do it however. Most have laptops mounted on a special rig so that it can be accessed from the drivers position. Depending upon the size of your vehicle this could interfere with the passenger. Otherwise its probably the best thing going.