Ubuntu/Debian network interface files
10th June 2009
Note to self: Example interface files for ubuntu/debian systems.
DHCP:
iface eth0 inet dhcp
Static:
iface eth0 inet static address 1.2.3.4 netmask 255.0.0.0 gateway 1.0.0.1
Now, don't forget it!
|
Note to self: Example interface files for ubuntu/debian systems.
DHCP:
iface eth0 inet dhcp
Static:
iface eth0 inet static address 1.2.3.4 netmask 255.0.0.0 gateway 1.0.0.1
Now, don't forget it!
When people use the term "Enterprise Information Technology", what kind of environment are people really talking about? For me, this term refers to the facilitation and management of integrated corporate information by software and hardware for medium to large organizations. Enterprise IT differs from IT at smaller organizations in both scale and the requirement of a lot more management and automation tools. Tools that work quite well in Small Office/Home Office (SOHO) environments often do not scale for larger organizations, do not address the correct problem or cannot integrate with the kinds of systems common to enterprise IT structures.
This is not to imply that SOHO applications are inferior or less robust. Even if application costs were not an issue, there are many enterprise IT applications that are simply not appropriate for SOHO environments due to hardware requirements, installation complexity, administrative overhead or missing network dependencies (for instance, some applications may require SNMP-aware switches that are lacking in most SOHOs).
The key attributes of an enterprise IT solution are scalability and integration. Scalability is the process by which an application may be altered to handle increasing amounts of usage. Notice that I said "process". Too many vendors tout scalability as a feature, which it is not. Application scale through many techniques, but all require the intervention of system administrators to implement. Google search engine, for instance, scales to millions of users searching billions of pages of content, but it requires thousands of commodity servers deployed in standard shipping containers distributed through the world. Without scalability, an application can meet the growing demands of the end-user.
Integration is the other distinguishing feature of IT software. Large IT systems must be able to exchange information with other IT systems in an automated way. For instance, a network management tool needs to be able to retrieve network statistics from smart switches and routers. SSLVPN routers need to be able to talk to a center Authentication and Authorization system, like Active Directory. Without integration, information gets repeated in individual applications. This creates the undesirable "siloization" of information that significately reduces the efficiency of IT departments and can even compromize security.
There are several components of enterprise IT that can be broadly categorized into the areas discussed in the next part of this essay, coming soon.
Every opinion looks better with a graph and no graph has captured my experience of working in software more than this.
The most fun part of working in tech is working in some niche that's climbing the Peak of Inflated Expectations. The inevitable Trough always comes, but there's a kind of doublethink that techies have that pretends this isn't the case. I believe this is instinct comes from the same self-preservation skill that allows us not to dwell too long upon our own impending mortalities.
In a small scale, I'm looking forward to the popcap war game Plants vs. Zombies which appears tomorrow.
The migration to the new theme here at the taskboy has gone well. Now it's time to pay for all of this.
As of today, I'm putting some Google AdWords on this site. The positioning is relatively hidden, but I think anyone looking for ads can find them easily enough.
To improve google's indexing of my site, I have created cached versions of all my blog entries (over 1200 pages!). The permalink format for the blog entries has changed a bit. I guess that makes the old links not very perma.
I will be adding more technical content here more regularly. I'll try to crank out a solid article every week with daily updates of my technical shenanigans.
Perhaps I'll even make some merch on Zazzle in the pursue of filthy Mammon.
If I feel the need for non-technical blogination, I'll either update my Facebook profile (which I'm loathe to do) or finally use my LiveJournal account.