Cold and Unsettled: LinuxWorld NYC 2003
I didn't make it to this show last year, so it's been a while since I've visited New York City. A lot has changed. Walking down Madison and Fifth Avenues this past Monday, MLK Day, the streets were mostly empty and about one quarter of the storefronts had "Space Available" signs posted.
Over breakfast I had read the New York Times for updates on the US's any-minute-now war plans. Now I was walking by the place where the World Trade Center once stood. Ground Zero is cleared now. Aside from the flowers and signs still present, it looks like any other piece of land ready for development. Not having seen the physical destruction beyond the television images, it's hard for me to reconcile this empty piece of real estate with my memories of visiting the WTC when I used to live on the East Coast.
So what does any of this have to do with LinuxWorld? I start with these moments in an attempt to explain why it feels weird to be here, LinuxWorld and NYC. I wrote the notes for this article while seated in the upper atrium of the Javits Center, where LW NYC takes place. Out the huge front windows, the Empire State Building is dead center. There's some sort of feeling here that I'm having trouble verbalizing.
Tuesday is the set-up day for LinuxWorld at the Javits and not too much is happening. The floor is full of unopened crates and boxes, carpets are still in rolls, Linux folks are catching up with one another. The work, though, is being done by the union workers. Which wouldn't be bad, some people note, if the workers actually did the work instead of staring at you staring at them. Welcome to New York.
I did a lap around the show floor in the afternoon; all the usual suspects are present, from Red Hat and SuSE to HP and IBM. The .org section looks like it has a few new faces and includes the politically active New York LUGs. The Ximian booth is huge and quite junglish in theme; Dell's presence is bigger than it was in the past; and SGI has the cool Altix machines on display--all three sizes. Microsoft is back; the booth is about four times as large as the one it had at LW San Francisco last August. They seem to be here promoting their .ASP net and embedded offerings. I also spent some time talking to MetiLinx representatives, who are excited to be attending their first LinuxWorld. MetiLinx is doing some interesting work with adaptive infrastructure management in platform-agnostic environments.
As for news, if there's big news for this show, no one is talking about it or even aware of it. Traditionally, this is the East Coast business show. One of the good things about LW NYC is exactly that, however; news of who else has partnered on a new Linux-based business project and who is using it. Overall, the show is a good indicator of what the upcoming business year might look like, business-wise, for open source and Linux. So it's all good news but not overly exciting. We'll see how the week plays out and if I'm proven wrong.
In the meantime, I'm going to spend my free time here in New York walking around (hopefully not acquiring frostbite as I do so), thinking about the future and trying to find out why this is all making me feel so unsettled.
Heather Mead is senior editor for Linux Journal.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide