Comment Re: What Would a Post-Email World Look Like? (Score 1) 314
It will resemble a world without UUCP, BBS, IRC or (heh) ICQ.
It's the norm now, except for people who knows what SMTP(S) / POP3(S) / IMAP(S) or a MUA etc is.
It will resemble a world without UUCP, BBS, IRC or (heh) ICQ.
It's the norm now, except for people who knows what SMTP(S) / POP3(S) / IMAP(S) or a MUA etc is.
Wish I had mod points!
I'm curious on this one. From when
And BTW I'm interested in other people's experience on this, i keep an eye in technology that i don't particularly like. Just in case.
* Yes, being working only on UNIX probably my view is distorted. But no, being working in data centers with mixed UNIX/MS systems in my experience the only MS stuff you see in those places is Exchange, some solitary ISA / IIS / ASP /
Netflix moves a huge amount of video on the web, so I doubt it's that unpopular. Most people seem to be accessing it on their TVs, XBoxes and Roku style set top boxes though.
Netflix FWIK is limited to the US market.
Sorry, Netflix is not available in your country... yet
(I'm in EU)
On top of that, who wants to rip Netflix streams when you can get way better quality on the Bittorrent version?
And when it's not even impossible to do it even now
Hi neighbor.
I cant agree more on what you say about the western "masters of puppets", expecialy in our region. Some of us more "blessed" than others in a point in time and all the opposite some other point in time.
I'm curious as what will happen next looking at the present, free market and finance mixed with greed and ignorance changed the world more than once, like this. What is different now is the new possibilities technology, especially instant communications and the big knowledge base that Internet brings in the table this time.
I'm albanian (from Albania, not Kosovo) BTW.
Why to forward X? ssh -D is your friend
Must of what you said is true and fair, but i call bullshit on this:
Debian was one of the reasons that AMD64 support is as good as it is under Linux. The Redhat, gentoo, and slackware users that use the 64bit versions are benefiting from Debian getting their distribution to run on 64 bit platforms for years.
FWIK it was Andi Kleen from SuSE to port linux's kernel on AMD64. Quick googling:
http://www.x86-64.org/pipermail/announce/2001-June/000020.html
That is not my experience. At all the places i've worked as a consultant in IT the only linux distro i've seen is RH. That is 10 years working on unix servers. Another thing that i've noticed is that non commercial distros are automatically banned, there should be some commercial entity with whom to share the blame when something goes wrong.
Maybe it's just Italy? I'm really curious on this.
Lol!
I'm sorry i don't have mod points.
While we are at this, once it happened to me to give some disk space to a DBA. That space was in a big storage, all baked by solid state disks. The day after i did it i got called from the DBA who started whining that it was slow. Went to his office and he showed me the "proof". It was this:
$ dd if=/dev/zero of=file_on_ssd count=8196000
Seems you've know only lame sysadmins. Like i've seen bad dba's. And judging on the RAID part of your comment (wich is something new for me and no, i'm not being sarcastic) seems you're talking about small servers. In my sysad experience, oracle or such had always been assigned some LUN from a big storage, on which i have no control and neither the expertise to configure. RAID is done in there, in hardware for the part involving HA as minimum. All i can do is volume management, chown that LUN (if raw partitions in use, or FS if not) to oraadmin and build the stripes based on the indications i get from the storage guy.
Trivial things like shared memory limits and such i know
Amen to that.
And even when you are right, it's you who have to proof it as you're the last arriving one in the place, possibly in a way that does not hurt the other guy.
Never been working on network (well, professionally i mean) but nearly always when there is some network problem NOC and NOC people get called, first thing they say is that there is no malfunction on our part. And strange enough problems get resolved after 5/30 minutes after the call.
Now, reading the post of a net guy and knowing the reaction of normal loosers that first thing to blame is the network i can understand why it is so. But when someone from operations calls means (i hope at least) that i've gone at least the burden of checking iptables/pf/ routes, ping, ndd, ethtool kstat, arp and all before bothering another soul like me.
Though people act different, i cant speak just for me.
[...]
More generally, we have a fundamental problem in the I/O area: UNIX. UNIX I/O has a very simple model, which is now used by Linux, DOS, and Windows. Everything is a byte stream, and byte streams are accessed by making read and write calls to the operating system. That was OK when I/O was slower. But it's a terrible way to do inter-machine communication in clusters today. The OS overhead swamps the data transfer. Then there's the interaction with CPU dispatching. Each I/O operation usually ends by unblocking some thread, so there's a pass through the scheduler at the receive end. This works on "vanilla hardware" (most existing computers), which is why it dominates.
This is true. Though you're underestimating "modern" os's. Though, think of it as defensive planning. Who knowed ~20+ years ago that we would have solid state disks? Who knowed we would have 10GB NICs? SATA?
But the foundamental design of IO streams works and is easily adapted on new devices. Add on that the simplicity of
[...]
The supercomputer interconnect people have been struggling with this for years, but nothing general has emerged.
RDMA via Infiniband is about where that group has ended up. That's not something a typical large hosting cluster could use safely.
Add to that fibrechannel. And NUMA is an old and tried technology.
Most inter-machine operations are of two types - a subroutine call to another machine, or a queue operation. Those give you the basic synchronous and asynchronous operations. A reasonable design goal is to design hardware which can perform those two operations with little or no operating system intervention once the connection has been set up, with MMU-level safety at both ends. When CPU designers have put in elaborate hardware of comparable complexity, though, nobody uses it. 386 and later machines have hardware for rings of protection, call gates, segmented memory, hardware context switching, and other stuff nobody uses because it doesn't map to vanilla C programming. That has discouraged innovation in this area. A few hardware innovations, like MMX, caught on, but still are used only in a few inner loops.
At the cost of my mood points or whatever, now i call bullshit.
Rings protection? Used at least in linux.
Call gates? You mean Sysenter? Used at least in linux from ~2002 if im not wrong
Segmented memory? Hello 32bits? Is that what you mean? Correct me if im wrong, but i thought it was a thing of the past.
Hardware context switching? You mean VMX (AMD) or SVM (Intel) ? At least on Linux those instructions are used.
C is the limiting on this? Please.
MMX? SSE/2 etc?
gcc -mmmx -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2
(talking about gcc because that is what i know, though im sure other compilers cane use those instructions too)
It's not that this can't be done. It's that unless it's supported by both Intel and Microsoft, it will only be a niche technology.
yep right.
If you want to put yourself on the map, publish your own map.
