I got a Kaypro 4 went I went off to college. I programmed on several different computers in High School, but that was the first that was really mine.
Still have it, even though I haven't fired it up in about twenty years.
A) What I meant was, it's easier for them to say it needs 64MB than it is to fully test on something less (even though they may think less will be OK,) and they're not going to get as much complaint as when memory was a buck a meg.
B) Last I checked, 512 was a lot bigger than 64, or even 192.
It would be far easier to harden something as small as a sidearm against EMP than something as large as a strategic bomber. And they DO harden strategic bombers against EMP.
Slackware comes with a script that allows you to have SysV init scripts, unsurprisingly called rc.sysvinit. I don't know which version of Slackware first had it, but the date in the file is 1999.
I like the simplicity of the "normal" Slackware method, but also like the abstraction of the SysV method as well. I use Slackware at home, and have used Solaris extensively for work, and having the option to use either method is best for me.
You may be to blame if someone steals your card, but I'll bet there are limits to your liability. Any loss beyond that limit gets eaten by the bank. And that money comes from everyone who uses that bank. Fraud and theft eventually comes out of everyone's pocket, and is; therefore, everyone's problem.
I agree. Computers haven't been the same since they got rid of the blinking lights. I can live without the reels of tape, but without the blinking lights, how can I tell that anything is happening?
Slashdot Mirror
I got a Kaypro 4 went I went off to college. I programmed on several different computers in High School, but that was the first that was really mine. Still have it, even though I haven't fired it up in about twenty years.
I'd go for Strong Bad singing "The System is Down" instead, but the red flashing lights would be cool.
Didn't the December issue of Playboy already declare the Half-Life 2 was the number one game of the year?
Yeah. Agreed. My point was that it's easier to bump the spec than test at minimum memory.
A) What I meant was, it's easier for them to say it needs 64MB than it is to fully test on something less (even though they may think less will be OK,) and they're not going to get as much complaint as when memory was a buck a meg. B) Last I checked, 512 was a lot bigger than 64, or even 192.
Best thing for the linux community? Good, maybe, but not best. After all, SCO lives ...
It'll probably work fine on less, but with memory so cheap these days, it's easy to change the "minimum spec" without too much grumbling.
It would be far easier to harden something as small as a sidearm against EMP than something as large as a strategic bomber. And they DO harden strategic bombers against EMP.
Slackware comes with a script that allows you to have SysV init scripts, unsurprisingly called rc.sysvinit. I don't know which version of Slackware first had it, but the date in the file is 1999.
I like the simplicity of the "normal" Slackware method, but also like the abstraction of the SysV method as well. I use Slackware at home, and have used Solaris extensively for work, and having the option to use either method is best for me.
You may be to blame if someone steals your card, but I'll bet there are limits to your liability. Any loss beyond that limit gets eaten by the bank. And that money comes from everyone who uses that bank. Fraud and theft eventually comes out of everyone's pocket, and is; therefore, everyone's problem.
I agree. Computers haven't been the same since they got rid of the blinking lights. I can live without the reels of tape, but without the blinking lights, how can I tell that anything is happening?
lizzardo
"The exception 'unknown exception' has been reacehed. lizzardo