There's another factor at work when losing weight. Lets say you are 40 pounds over weight. That is 40 pounds additional that you are carrying during your normal daily activities. Now if you start exercising, change diet, etc., you may lose 20 pounds, but then stop losing weight. That's because when you aren't working out that is 20 pounds less that you have on you when, say, walking form the couch to the fridge, etc. So you won't be able to lose that extra 20 pounds unless you work out even more. This will apply to anyone who is over weight, but at a stable weight (i.e., they never go above X pounds over their ideal weight).
So here's my thought. What about wearing a weighted belt. Whenever you drop 5 pounds, add a 5 pound weight to the belt. This way you are always carrying that extra weight with you, so your body will stabilize at a lower number.
Yes, patents cover any imports. Also according to the statutes wording it is also a violation to manufacture, import, or distribute a kit composed of non-patented items if it violates a patent when assembled. So since the vendors have to include the source code, even if the code is compiled in such a way to avoid the patent the source itself would still be in violation of the patent statute. See US Code TITLE 35 PART III CHAPTER 28 S 271 (c).
Just recently I had to update the firmware on a qlogic card. The updater ws a stand alone Dos exe file. No linux Windows version available, and they didn't even ship a self booting floppy image. The only way to update the server was to download freedos. That, combined with a bit of magic using grub and memdisk worked perfectly.
The original Doom didn't use hardware 3D -- I remember playing it on a 286 system with ease. Of course, the graphics were 320x200, and the most basic of 3D effects. But that was all software driven.
Also, I'd count Flight Simulator in as a 3D game. The original one by Bruce Artwick ran on Commodore, Atari, 8088 PCs, etc. And the 3D in that was only one step down from what was in Doom (polygon graphics without a texture overlay, but with light source direction).
Or the Nokia n810, which you can get for $200 now. Or wait for the next gen tablet. Actually, the next Maemo device coming from Nokia is actually going to be a phone, not a tablet, but rummer has it that they are still planning more tablet models.
That's something I don't understand. If they are trucks, then why don't they have "B" license plates? In Chicago, there's some roads that you can't drive a pickup truck on (they have a sign saying no trucks, and the police enforce that against anything with a B plate). Yet the SUVs are allowed on them. Not fair.
Before slackware there was SLS (Soft Landing Systems). The sysop of a BBS that I downloaded a bunch of Unix utilities from had offered to copy it onto floppies for you, if you sent him the box of floppies & return postage. Took 15 floppies I believe.
Before that, I had used what probably can't be called a distribution -- it consisted of a boot floppy, and a root floppy. From there, you could fdisk a partition, and also used DOS debug to modify a particular byte offset on the kernel boot floppy to tell it to load the root filesystem from your hard drive.
But unless you are running benchmarks, can you really feel a 5% increase? Personally, I don't see any results unless the speed increases by at least 50% more. Unless you have hard real-time dependencies (such as video or certain games). But in those cases, you usually either have extra cpu cycles to burn, or you need more than a mere 5% to do any good.
I had picked up a game back in the 90's that was based on this. I think it was from a company called "The other 90% technologies" or something like that. It had a sensor that you hooked up to a finger, and you could control a downhill skier. You had to "think hard right", and "relax left".
arrl.org (the American Radio Relay League). Also, the electronic department of most community colleges have a ham club, which offer the tests on a monthly basis.
You don't need to know Morris code any more, but you do need to study up on radio & electronic theory. Radio shack used to sell the Ham license study guides, but I don't know if they have them any more.
But Windows won't run on the next generation of netbook computers (the ARM-based ones, such as what Freescale/Pegatron is comming out with). Unless you count WinCE. But Linux will run the same apps as always, since everything can be (and has been) ported.
Of course, this hinges on the assumption that ARM-based netbooks will take off, and I think they will. For one thing, they get much better battery life than you can get out of an x86 (even though Atom is low powered, you still have the thirsty chipset). And the prices are better than most of the x86 netbooks ($100 to $200).
If that's the case, then why don't they use a BSD-like license? Because that's all they will have if copyrights are eliminated -- anyone can take FSF code, modify it, and lock away their modifications.
I'd rather they set up traffic shaping, so that as your "rolling average" usage increases your effective bandwidth decreases. That way, if you've used only 20GB/month for the last week (so 5 GB in that week), you would get your full rate. But use 10GB in that time frame, and you will get 80% of your allotment, and so on. But the most import thing would be to have a guaranteed minimum allotment, and have it so that you don't get a sudden large drop (like from 10Gb to 128Kb). It should be a smooth curve.
They may up the megahertz, but not at the expense of a more costly product or more power usage. Instead, the ARM chip vendors take a look at what needs the MHZ, such as video/audio decoding, and include special co-processors for those functions on the same silicon. Therefore they don't need to increase MHz for increased functionality.
It is a similar philosophy to using a script written in a slow interpreted language to drive a more complex system composed of high-speed modules written in C.
Instead of giving apps the ability to tag "critical" data, give them the ability to inspect the write status of data. This can be done by adding adding another fd_set to select() (which currently has readfds, writefds, and exceptfds). Add one called "flushedfds" that will return when all data for that file descriptor has been flushed to disk. The kernel can prioritize flushes for all files that have an active select(...flushedfds...) call pending, but otherwise it can still do writes in the optimal order. And the app can have its guarantee that critical data has been written.
I can personally vouch for that. I started cycling to work last summer, mostly because of the high gas prices. Of course, come winter I had to go back to driving, and with lower gas prices I'm not sure that I'll get back in shape to do the cycling thing again (only 15 miles each way, but then there's getting up early, having to shower at the fitness center at work, not able to haul many books / laptop, etc).
But if gas was pushing $5.00 a (US) gallon again, I'd be investing in cold-weather cycling gear, additional saddle bags, a better cycle, etc.
I can almost make out the whole thing, but where did that "a" with the "^" over it, followed by the quote character, come from? I don't remember seeing that in the original Mark Twain quote.
But the payroll withholding ends up being a tax on your employer. Because when you negotiate your salary, you do so knowing that a big chunk is taken out in taxes. So if you want to make $3000 a month, you ask for $4500. But if you didn't have any taxes coming out, then your employer would probably be able to talk you down to paying $3000 a month, and you would be happy (otherwise, there would be enough other people willing to do that job for that price).
I'd actually like to see a good comparison between different modern systems where taxes are taken out before you get your money, vs. taxes collected in some other manner (not based off income). Then compare the typical income for particular jobs to the price of goods & services.
Well, it is a bit more involved than a simple script with ssh in a for loop, when you have a large number of systems (and I'm speaking from experience with servers, not desktops). A system may be unreachable, so you have to record that attempt as a failure to retry later. Or a machine could be reachable, but running very slowly -- which will not fail the ssh attempt, but it will run too slowly on that host so that your loop doesn't finish in a reasonable time.
Or, if you have a job that takes a few minutes on each host, then you need to run several ssh sessions in parallel. But not too many at a time, otherwise you could run out of sockets on your master host.
So what I did was set up a script that would run N ssh sessions in parallel. When a session terminated, it's result was recorded in a log file and a new session would take it's place (so there were always N jobs running). If a job ran for longer than TIMEOUT, then it would get killed and logged.
We used to go a step further, when we had a bunch of NCD X terminals at my previous shop (about 10 years ago). The user didn't own their own home directory (therefore couldn't write to it). That meant that files such as.profile couldn't be changed. Any file that needed to be written to was symlinked to a file $HOME/myhome, which was owned by that user. Also, $HOME/Documents and such were also owned by that user. The upshot is that additional lockdowns could be put in their.profile, without the user being able to edit it if they got to a shell prompt from some other method.
You can use Gizmo to set up a SIP number, which is free to use with other SIP numbers. Then use Google's GrandCentral to connect a POTS number to your Gizmo SIP number. Now you've got free incoming POTS calls. For right now, GrandCentral also lets you do free outgoing calls through it's web interface (there are also other front-end clients that automate this for you). That part is free during their Beta period, but you know how long Google's betas go on.
There's another factor at work when losing weight. Lets say you are 40 pounds over weight. That is 40 pounds additional that you are carrying during your normal daily activities. Now if you start exercising, change diet, etc., you may lose 20 pounds, but then stop losing weight. That's because when you aren't working out that is 20 pounds less that you have on you when, say, walking form the couch to the fridge, etc. So you won't be able to lose that extra 20 pounds unless you work out even more. This will apply to anyone who is over weight, but at a stable weight (i.e., they never go above X pounds over their ideal weight).
So here's my thought. What about wearing a weighted belt. Whenever you drop 5 pounds, add a 5 pound weight to the belt. This way you are always carrying that extra weight with you, so your body will stabilize at a lower number.
Yes, patents cover any imports. Also according to the statutes wording it is also a violation to manufacture, import, or distribute a kit composed of non-patented items if it violates a patent when assembled. So since the vendors have to include the source code, even if the code is compiled in such a way to avoid the patent the source itself would still be in violation of the patent statute. See US Code TITLE 35 PART III CHAPTER 28 S 271 (c).
Just recently I had to update the firmware on a qlogic card. The updater ws a stand alone Dos exe file. No linux Windows version available, and they didn't even ship a self booting floppy image. The only way to update the server was to download freedos. That, combined with a bit of magic using grub and memdisk worked perfectly.
The original Doom didn't use hardware 3D -- I remember playing it on a 286 system with ease. Of course, the graphics were 320x200, and the most basic of 3D effects. But that was all software driven.
Also, I'd count Flight Simulator in as a 3D game. The original one by Bruce Artwick ran on Commodore, Atari, 8088 PCs, etc. And the 3D in that was only one step down from what was in Doom (polygon graphics without a texture overlay, but with light source direction).
Or the Nokia n810, which you can get for $200 now. Or wait for the next gen tablet. Actually, the next Maemo device coming from Nokia is actually going to be a phone, not a tablet, but rummer has it that they are still planning more tablet models.
That's something I don't understand. If they are trucks, then why don't they have "B" license plates? In Chicago, there's some roads that you can't drive a pickup truck on (they have a sign saying no trucks, and the police enforce that against anything with a B plate). Yet the SUVs are allowed on them. Not fair.
Yeah, it's gotten to the point where my response to most of these studies is "Thank God I'm not a rat".
What about when companies merge, or otherwise have to connect networks? Two companies using 10.x could have overlapping IPs.
Before slackware there was SLS (Soft Landing Systems). The sysop of a BBS that I downloaded a bunch of Unix utilities from had offered to copy it onto floppies for you, if you sent him the box of floppies & return postage. Took 15 floppies I believe.
Before that, I had used what probably can't be called a distribution -- it consisted of a boot floppy, and a root floppy. From there, you could fdisk a partition, and also used DOS debug to modify a particular byte offset on the kernel boot floppy to tell it to load the root filesystem from your hard drive.
But unless you are running benchmarks, can you really feel a 5% increase? Personally, I don't see any results unless the speed increases by at least 50% more.
Unless you have hard real-time dependencies (such as video or certain games). But in those cases, you usually either have extra cpu cycles to burn, or you need more than a mere 5% to do any good.
I had picked up a game back in the 90's that was based on this. I think it was from a company called "The other 90% technologies" or something like that. It had a sensor that you hooked up to a finger, and you could control a downhill skier. You had to "think hard right", and "relax left".
I've got flash on my Nokia N800, which is an arm-based processor. And this line of internet tablets have been out for a few years now.
arrl.org (the American Radio Relay League). Also, the electronic department of most community colleges have a ham club, which offer the tests on a monthly basis.
You don't need to know Morris code any more, but you do need to study up on radio & electronic theory. Radio shack used to sell the Ham license study guides, but I don't know if they have them any more.
But Windows won't run on the next generation of netbook computers (the ARM-based ones, such as what Freescale/Pegatron is comming out with). Unless you count WinCE. But Linux will run the same apps as always, since everything can be (and has been) ported.
Of course, this hinges on the assumption that ARM-based netbooks will take off, and I think they will. For one thing, they get much better battery life than you can get out of an x86 (even though Atom is low powered, you still have the thirsty chipset). And the prices are better than most of the x86 netbooks ($100 to $200).
If that's the case, then why don't they use a BSD-like license? Because that's all they will have if copyrights are eliminated -- anyone can take FSF code, modify it, and lock away their modifications.
I'd rather they set up traffic shaping, so that as your "rolling average" usage increases your effective bandwidth decreases. That way, if you've used only 20GB/month for the last week (so 5 GB in that week), you would get your full rate. But use 10GB in that time frame, and you will get 80% of your allotment, and so on. But the most import thing would be to have a guaranteed minimum allotment, and have it so that you don't get a sudden large drop (like from 10Gb to 128Kb). It should be a smooth curve.
They may up the megahertz, but not at the expense of a more costly product or more power usage. Instead, the ARM chip vendors take a look at what needs the MHZ, such as video/audio decoding, and include special co-processors for those functions on the same silicon. Therefore they don't need to increase MHz for increased functionality.
It is a similar philosophy to using a script written in a slow interpreted language to drive a more complex system composed of high-speed modules written in C.
Connect a long cable to the craft with a counterweight, and spin the whole thing. The counterweight could be another ship module for redundancy.
Instead of giving apps the ability to tag "critical" data, give them the ability to inspect the write status of data. This can be done by adding adding another fd_set to select() (which currently has readfds, writefds, and exceptfds). Add one called "flushedfds" that will return when all data for that file descriptor has been flushed to disk. The kernel can prioritize flushes for all files that have an active select(...flushedfds...) call pending, but otherwise it can still do writes in the optimal order. And the app can have its guarantee that critical data has been written.
I can personally vouch for that. I started cycling to work last summer, mostly because of the high gas prices. Of course, come winter I had to go back to driving, and with lower gas prices I'm not sure that I'll get back in shape to do the cycling thing again (only 15 miles each way, but then there's getting up early, having to shower at the fitness center at work, not able to haul many books / laptop, etc).
But if gas was pushing $5.00 a (US) gallon again, I'd be investing in cold-weather cycling gear, additional saddle bags, a better cycle, etc.
I can almost make out the whole thing, but where did that "a" with the "^" over it, followed by the quote character, come from? I don't remember seeing that in the original Mark Twain quote.
But the payroll withholding ends up being a tax on your employer. Because when you negotiate your salary, you do so knowing that a big chunk is taken out in taxes. So if you want to make $3000 a month, you ask for $4500. But if you didn't have any taxes coming out, then your employer would probably be able to talk you down to paying $3000 a month, and you would be happy (otherwise, there would be enough other people willing to do that job for that price).
I'd actually like to see a good comparison between different modern systems where taxes are taken out before you get your money, vs. taxes collected in some other manner (not based off income). Then compare the typical income for particular jobs to the price of goods & services.
Well, it is a bit more involved than a simple script with ssh in a for loop, when you have a large number of systems (and I'm speaking from experience with servers, not desktops). A system may be unreachable, so you have to record that attempt as a failure to retry later. Or a machine could be reachable, but running very slowly -- which will not fail the ssh attempt, but it will run too slowly on that host so that your loop doesn't finish in a reasonable time.
Or, if you have a job that takes a few minutes on each host, then you need to run several ssh sessions in parallel. But not too many at a time, otherwise you could run out of sockets on your master host.
So what I did was set up a script that would run N ssh sessions in parallel. When a session terminated, it's result was recorded in a log file and a new session would take it's place (so there were always N jobs running). If a job ran for longer than TIMEOUT, then it would get killed and logged.
We used to go a step further, when we had a bunch of NCD X terminals at my previous shop (about 10 years ago). The user didn't own their own home directory (therefore couldn't write to it). That meant that files such as .profile couldn't be changed. Any file that needed to be written to was symlinked to a file $HOME/myhome, which was owned by that user. Also, $HOME/Documents and such were also owned by that user. The upshot is that additional lockdowns could be put in their .profile, without the user being able to edit it if they got to a shell prompt from some other method.
You can use Gizmo to set up a SIP number, which is free to use with other SIP numbers. Then use Google's GrandCentral to connect a POTS number to your Gizmo SIP number. Now you've got free incoming POTS calls. For right now, GrandCentral also lets you do free outgoing calls through it's web interface (there are also other front-end clients that automate this for you). That part is free during their Beta period, but you know how long Google's betas go on.