put tinfoil in your wallet, or put the cards in a tinfoil closure.
so the legacy found anotherway:
dolby mobile so its not just tapes and home cinema stuff...
I used the eee 701 before and own now a ACER aspire one pro with 250GB HD, 2 GB RAM, bluetooth and UMTS modem. The 701 was nice to have but due to the small display and keyboard you couldn't really use it. The aspire one is great. It's fine for browsing, writing and even drawing. But I haven't tested any CPU intensive workloads, like VM or gaming. By now the aspire has replaced my old 1.5 GHz Centrino notebook (15").
These days I would probably choose a netbook with AMD C-XX APU (e.g. aspire one 522): quite powerful GPU and up to 10 hours battery life.
Do Mär 25 2010 14:51:25 EDT von LoanShark @ Uncensored
Get rid of those pesky indexes too; they just consume disk space.
having a non-ascii interface to it doesn't say anything about which technologies should be applied for looking up and storing the data
and *definitely* nobody wants to use a "record manager with
transaction support" directly. That's just a non-starter for any heavy
I'm not sure I get that.
Deep down beneath all those layers upon layers upon layers of crap, way in the bowels of oracle, is something akin to a record manager.
So, what you're really saying is that you can't trust a record manager unless there's tons of saftey layer crap on top of it
Is there a name for the concept of setting a dchp server (or more
importantly my wireless router) to hand out the same ip address to a
particular mac address every time it connects. effectively giving it a
static ip without changing anything on the client?
The official name for that is a "reservation." But as has been mentioned in the last few messages, it's often called other things depending on who built your DHCP server software.
Ford: Ok sure it's not the be-all end-all. But it is the /minimum requirement/ for a functional system. It's the best mapping to the relational calculus. And maybe you could say "ok, I don't want programmers embedding SQL strings in code, I want a type safe query api instead." But you still end up with the requirement that your query criteria api has to work along the same lines as sql: Ideally it has to be a functional superset of SQL (and SQL still needs to be available as an option for those technical end users.) And that query api.. has to work along similar lines: it has to delegate all the details of access path optimization to the engine, or at least encapsulate the details within reasonable defaults. It has to present your application with a view of the relational calculus... not just binary blob records. Anything less is just too low level for a busy-busy programmer to have to b bothered to deal with.
have been researched since the 80s, no way a new idea, just a point
where technology felt the need for change, beutification,
naturalization, and GIMICKS!
Oh yes, the big bad evil DBA, who wants to "make you use nonportable
stuff." (Huh? WTF?)
I ask (although lately it's been turning into 'tell' and 'yell') my dba to create table X. I have him do it so he can add all the silly index names I could care less about and data segments and what not.
And what do I find?
I find foreign key constraints from my table against a new table that he made. He took my data out of my dev table and decided those were all the values that could be in my 'type' field so he made another table just so he could add forign key constraints against it.
Not my idea, I didn't ask him to, and it certainly didn't have prod or preprord ready data in it.
non portable isn't the only problem with some DBAs.
That's just what a lot of people need, though. I've got a Dell PowerEdge 2650 sucking down power in my basement 24 hours a day. Do I need all that power all the time? Of course not. I would welcome a box that sips power, especially during the 99% of the day when it's idle.
His data isn't THAT important.
If he only wrote over the directory tree, then he should start learning about how filesystems work and try and piece it together himself.
Do they still make sector editors anymore?
KVM is also half baked right now, so there's no point in using it yet. However, since it is backed by everyone who matters, KVM will inevitably become *the* open source hypervisor.
Give it a couple of years to shake out. Three years from now, all new deployments will be either VMware (because it's the best, by far), KVM (because it will be *the* open source choice), and Hyper-V (because the world is still full of stupid people who choose Microsoft products).
In the meantime, it's VMware's game.