Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Michael H. Warfield wrote: > On Sun, Feb 18, 2001 at 12:00:03PM -0600, Gregory S. Youngblood wrote: > > > I remember being at a computer show in Minneapolis where a small company > > was showing off this mouse that worked on a variety of surfaces without a > > ball. I'm trying to remember if the mouse was optical or used yet another > > method of functioning -- I think it was optical, though I could be > > mistaken. This was in 1992/1993. > > I think you are correct here. I seem to recall mention of some > of those earlier devices at the time of the Microsoft announcement. I > seem to also recall some of the reliability problem they had. I believe > they were extremely fussy about the surface they were on. In the demo I saw, they had about 6 sample surfaces ranging from a mirror to blue jeans. I also got to play with the mouse on the demo system and it worked very well. At the time, mice were about $25 to $35 dollars, and theirs were like $79 or $99. I remember thinking it was a cool toy, but the price difference was going to keep it from mass market potential. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Michael H. Warfield wrote: > On Sat, Feb 17, 2001 at 09:15:08PM -0800, Ben Ford wrote: > > > > > > On the other hand, they make excellent mice. The mouse wheel and > > > the new optical mice are truly innovative and Microsoft should be > > > commended for them. > > > > > The wheel was a nifty idea, but I've seen workstations 15 years old with > > optical mice. It wasn't MS's idea. > > I think their "innovation" was not requiring the optical cross > grid mouse pad common on Sun workstations over the years. The Microsoft > optical mouse uses variations in the surface characteristics of whatever > it's on to perform it's function. The old optical mice just used two > different colors of LED's (red and IR) and a special pad. This would > actually have to scan and track the surface below it. Don't know that > I've seen anyone do that before. I remember being at a computer show in Minneapolis where a small company was showing off this mouse that worked on a variety of surfaces without a ball. I'm trying to remember if the mouse was optical or used yet another method of functioning -- I think it was optical, though I could be mistaken. This was in 1992/1993. The point is, I really do not believe Microsoft made the "leap" to provide opitcal mice without the need of the mousepad grid. Their "innovation" was in marketing it on a wide scale though. I could be mistaken - if so then let's give them their credit - but I have a hard time believing it was their idea without some serious proof. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Michael H. Warfield wrote: On Sat, Feb 17, 2001 at 09:15:08PM -0800, Ben Ford wrote: On the other hand, they make excellent mice. The mouse wheel and the new optical mice are truly innovative and Microsoft should be commended for them. The wheel was a nifty idea, but I've seen workstations 15 years old with optical mice. It wasn't MS's idea. I think their "innovation" was not requiring the optical cross grid mouse pad common on Sun workstations over the years. The Microsoft optical mouse uses variations in the surface characteristics of whatever it's on to perform it's function. The old optical mice just used two different colors of LED's (red and IR) and a special pad. This would actually have to scan and track the surface below it. Don't know that I've seen anyone do that before. I remember being at a computer show in Minneapolis where a small company was showing off this mouse that worked on a variety of surfaces without a ball. I'm trying to remember if the mouse was optical or used yet another method of functioning -- I think it was optical, though I could be mistaken. This was in 1992/1993. The point is, I really do not believe Microsoft made the "leap" to provide opitcal mice without the need of the mousepad grid. Their "innovation" was in marketing it on a wide scale though. I could be mistaken - if so then let's give them their credit - but I have a hard time believing it was their idea without some serious proof. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Michael H. Warfield wrote: On Sun, Feb 18, 2001 at 12:00:03PM -0600, Gregory S. Youngblood wrote: I remember being at a computer show in Minneapolis where a small company was showing off this mouse that worked on a variety of surfaces without a ball. I'm trying to remember if the mouse was optical or used yet another method of functioning -- I think it was optical, though I could be mistaken. This was in 1992/1993. I think you are correct here. I seem to recall mention of some of those earlier devices at the time of the Microsoft announcement. I seem to also recall some of the reliability problem they had. I believe they were extremely fussy about the surface they were on. In the demo I saw, they had about 6 sample surfaces ranging from a mirror to blue jeans. I also got to play with the mouse on the demo system and it worked very well. At the time, mice were about $25 to $35 dollars, and theirs were like $79 or $99. I remember thinking it was a cool toy, but the price difference was going to keep it from mass market potential. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: problems with grow_inodes: inode-max limit reached
On 7 Nov 2000, Chmouel Boudjnah wrote: > "Gregory S. Youngblood" <[EMAIL PROTECTED]> writes: > > > The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16, > > and 2.2.17. These are the secure kernels that Mandrake provides. > > can you try with a 2.2.17 kernel rpm standard (no smp no secure) ? I rebooted with the 'failsafe' kernel, which is 2.2.17 no smp no secure per your request. If the pattern holds, I will have an update with a failure (if it fails) within the next 24 to 72 hours. Thanks, greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
problems with grow_inodes: inode-max limit reached
I've got a problem with inodes which spans three kernels when used as a gateway/firewall. The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16, and 2.2.17. These are the secure kernels that Mandrake provides. The catch is, it only affects one machine - the machine I set up as a gateway which is using rp-pppoe and acting as a gateway/firewall for a windows and linux machine in a small network. As well as using ipmasqadm for port forwarding. The system works flawlessly, for about 24 to 72 hours. Then I start getting: grow_inodes: inode-max limit reached repeatedly Once this happens, I can't log in or reboot the system or access any files on the system. The network connections appear to still work, as I don't lose connecitivity with anything I'm currently connected to. By default, the inode-max is 4096 on this sytem (a compaq deskpro 5133, 32 meg RAM). I've upped it to 131072 to try and buy some time. The problem does NOT appear on either of my other linux workstations, one of which has been up for 119 days with a login since Jul 11, 2000, and the other which has been up for 30+ days at a time. The workstations run a variety of items, including X, MySQL, PostgreSQL, httpd, sshd, and a variety of other daemons. The gateway/firewall ONLY has sshd and other minimal daemons, nothing more. (these other systems are also mandrake 7 using the same secure kernels 2.2.14 and 2.2.16). I've done several searches for information on this problem, and so far the only useful information I've found was someone suggesting resetting the indoe-max value, which I've done. But, that still doesn't answer the original problem. Does anyone have any ideas on what is causing these problems? Or how to fix it once and for all? Greg PS: The machine in question is configured: Compaq Deskpro 5133, P-133, 32 meg RAM, 1.2 gig IDE hard drive, Intel etherexpress pro 10/100, smc eznet 10/100 running Mandrake 7.1 with kernel 2.2.17 (Mandrake 2.2.17-21mdksecure). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
problems with grow_inodes: inode-max limit reached
I've got a problem with inodes which spans three kernels when used as a gateway/firewall. The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16, and 2.2.17. These are the secure kernels that Mandrake provides. The catch is, it only affects one machine - the machine I set up as a gateway which is using rp-pppoe and acting as a gateway/firewall for a windows and linux machine in a small network. As well as using ipmasqadm for port forwarding. The system works flawlessly, for about 24 to 72 hours. Then I start getting: grow_inodes: inode-max limit reached repeatedly Once this happens, I can't log in or reboot the system or access any files on the system. The network connections appear to still work, as I don't lose connecitivity with anything I'm currently connected to. By default, the inode-max is 4096 on this sytem (a compaq deskpro 5133, 32 meg RAM). I've upped it to 131072 to try and buy some time. The problem does NOT appear on either of my other linux workstations, one of which has been up for 119 days with a login since Jul 11, 2000, and the other which has been up for 30+ days at a time. The workstations run a variety of items, including X, MySQL, PostgreSQL, httpd, sshd, and a variety of other daemons. The gateway/firewall ONLY has sshd and other minimal daemons, nothing more. (these other systems are also mandrake 7 using the same secure kernels 2.2.14 and 2.2.16). I've done several searches for information on this problem, and so far the only useful information I've found was someone suggesting resetting the indoe-max value, which I've done. But, that still doesn't answer the original problem. Does anyone have any ideas on what is causing these problems? Or how to fix it once and for all? Greg PS: The machine in question is configured: Compaq Deskpro 5133, P-133, 32 meg RAM, 1.2 gig IDE hard drive, Intel etherexpress pro 10/100, smc eznet 10/100 running Mandrake 7.1 with kernel 2.2.17 (Mandrake 2.2.17-21mdksecure). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
