Domain: netadmintools.com
Stories and comments across the archive that link to netadmintools.com.
Comments · 8
-
nice java
I don't see why these "cinder" features can't be delivered by realtime UI to nice and with a Java sandbox. In other words, Android or any other Linux phoneOS, with a little tweak wiring top to nice, and a Java VM. App running slow, crank out the "nice" level, and it will suck more juice as it runs faster than the other apps left out of the juice rotation. Put the UI in terms of power instead of CPU, and you're groovy.
-
nice java
I don't see why these "cinder" features can't be delivered by realtime UI to nice and with a Java sandbox. In other words, Android or any other Linux phoneOS, with a little tweak wiring top to nice, and a Java VM. App running slow, crank out the "nice" level, and it will suck more juice as it runs faster than the other apps left out of the juice rotation. Put the UI in terms of power instead of CPU, and you're groovy.
-
Avoid WHOIS for initial search - my web form
Along a similar vein, I wrote this web form that uses dig about a year ago when I contemplated buying several domain names. I wanted a tool to minimize the chance of front-running happening to me, which means avoiding WHOIS lookups.
It uses the Linux dig command (man page), which amounts to a DNS lookup, to guess if the domain is registered. It's not bulletproof. There are occasional false-negatives if someone has registered a domain but hasn't set up DNS for it. Someday they'll snoop DNS lookups, but that doesn't seem to be the case just yet - besides DNS lookups don't necessarily go through NSI servers, or do they? -
Re:Because it is a big deal, IMHO.Some of the things you're talking about aren't making sense to me, honestly.
I'm looking forward to DX10
I'm not a gamer, so I could care less. If I want to play games, I'll use a console.lower CPU usage (because the UI is run on the GPU)
Lower CPU usage than what? XP? I've run XP on a 500 MHz with a 320 meg ram and a whopping 4 meg vid card and it's still usable. Vista _requires_ an 800 MHz CPU and a half-gig of ram (one gig preferred) minimum. You call that LOWER usage? If the UI is run on the (128 MB _minimum_) GPU, why should the CPU requirements be HIGHER?the ability to prioritize I/O (no more 10 fps in games if you move big files around on your computer at the same time)
That's nice...SMB 2.0 (transfers should survive now if the network is disconnected for a moment)
Good lord, things like ssh have been able to do that for almost a decade. You can even restart networking/samba/ftp service on a remote machine via a remote shell and not lose your connection.virtualized registry
The registry is perhaps one of Microsoft's biggest blunders, in my opinion. Having a single point of failure for the entire system is just a Bad Idea(TM).improved windows APIs (this is mostly for us programmers)
I'm not a programmer, so I won't comment.improved audio system (ability to mute/adjust sound per application instead)
Don't most things like that include a volume control within the app itself? I may be mistaken on the concept though, that's for sure.multitasking of GPUs
If you've got more than one GPU, I would hope to god they'd be multitasking.general bugfixes
After 5 years, you'd hope there would be some bugfixing going on, instead of just dumping much touted features (i.e. winfs)improved stability
The jury's still out on that one, mostly because the general public hasn't used it and been clicking on every thing that pops up in their face all the time... mostly only computer savvy people that know how to keep their systems stable in the first place have been running the betas.A better question would be why some people (excluding mac & linux users
:) are not looking forward to Vista? Aside from the DRM (which will be promptly cracked), that is.
Why exclude mac & linux users? Are they not computer users?
#1 Cost - increased hardware requirements, in the license, loss of rights to do with what we buy as we see fit
#2 Cracked DRM? Is that even legal? AFAIK, it's punishable by law.
I'm sure others could provide more. However, #1 is the show stopper for me. -
phoning home goes back to 2000 or more
Microsoft has phoned home for a long time. I've seen reports of this as early as June, 2000. I'm sure there are earlier instances. Now, to be fair, Firefox phones home for updates. I don't remember seeing a big warning that this was done, or what data was saved at the server, but I like the feature. Of course, if Microsoft is so worried about this app running that they want the chance to turn it off at a days notice as they claim, then, well, this is in a different class of phoning home.
-
history
There is a history of this issue and related links here. The castlecops stuff has threads of the original spam message board threads.
-
OS X and noexec
Just like you would any other directory on any other Unix: pass "noexec" as a flag to the mount command that creates the tmp directory (http://www.netadmintools.com/html/8mount.man.htm
l ):
mount -o remount,noexec /tmp -
Re:Lucky me
Although I find the click-kiddy label amuzing it doesn't apply. I know how to properly manage my DNS setup and I know how caching works, that's why I had modified the TTL and negative cache settings well in advance.
See this page if you need some more info about TTL's and IP migration:
http://www.netadmintools.com/art232.html
This IP migration was well-planned but for some reason zoneedit (my secondary) started refusing notifies from my primary DNS.