This Year's Ottawa Linux Symposium Covered 51
cdlu writes "This year's Ottawa Linux Symposium was well-attended and hosted numerous very interesting discussions. There's extensive coverage at NewsForge: (comprehensive day 1,
day 2,
day 3, and
day 4, Linux Weekly News (subscription): A challenge for developers, Linux and trusted computing, and Xen and UML, and O'Reilly network: First day and Wrap up."
Location? (Score:1, Funny)
Re:Location? (Score:1)
Ottawa, Ontario Canada
Re:Location? (Score:1)
The sequel already? (Score:1, Funny)
Spammer: (Score:2)
Enough with the irrelevant details (Score:5, Funny)
Ottawa Linux? (Score:2, Funny)
LUG Radio Live was also held recently... (Score:5, Informative)
See http://www.lugradio.org/live/2005/ [lugradio.org] for all the exciting news, blogs and photos.
bah!
why didn't I know about it? (Score:4, Interesting)
I'm not a hardcore linux geek, but I watch the news, read the paper, and I'm on slashdot every day. You guys are going to *have* to do a better job advertising this!
Sam
Re:why didn't I know about it? (Score:3, Informative)
Re:why didn't I know about it? (Score:2)
Re:why didn't I know about it? (Score:4, Informative)
I didn't know about the Linux symposium. I would have gone.
The kernel summit is by invitation only
The Kernel Summit is a separate event that occurs the week before the Ottawa Linux Symposium. The Kernel Summit is invitation-only. In contrast, anyone who buys a ticket can attend OLS. Most of the developers (except, notably, Linus) who attend the Kernel Summit also attend OLS. Typically the opening speech at OLS is a summary of what decisions were made at the summit. The summit is where the real near-term hard decisions are hashed out; OLS tends to focus on emerging technologies and has less of an influence over the near-term direction of the core kernel development.
Re:why didn't I know about it? (Score:1, Informative)
You can sign up here:
http://lists.linuxsymposium.org/mailman/listinfo/
Re:why didn't I know about it? (Score:4, Interesting)
Make sure you get in early for next year--it's way cheaper that way.
Re:why didn't I know about it? (Score:2)
Re:why didn't I know about it? (Score:1)
Re:why didn't I know about it? (Score:2)
and you didn't notice the plethora of drunk geeks at all the local bars?
Re:why didn't I know about it? (Score:2)
They've always expressed more of an interest in getting the right people together than in being as large as possible.
So if you're not a "hardcore linux geek", maybe it's not really the event for you. It's mainly a chance for linux developers to get together and discuss their work.
Re:why didn't I know about it? (Score:2)
I'm not a hardcore linux geek, but I watch the news, read the paper, and I'm on slashdot every day. You guys are going to *have* to do a better job advertising this!
Yes, It's always the same, but I'd say that it's the fault of the media. The Ottawa Linux Symposiom is pretty well know all over the world, but the mainstream media is not interested in it. If you have an idea to promote the event we'd be glad to get your suggestion.
Nice XP presentation though (Score:5, Interesting)
Re:Nice XP presentation though (Score:1)
Re:Nice XP presentation though (Score:2)
Everywhere but their presentation, it seems
Note: I wasnt there so I really dont know...
Re:Nice XP presentation though (Score:1)
Proceedings (Score:4, Interesting)
http://www.linuxsymposium.org/2005/linuxsymposium
http://www.linuxsymposium.org/2005/linuxsymposium
NewsForge and Slashdot are both part of... (Score:2, Interesting)
For those who don't know (Score:1, Offtopic)
Obvious reference (Score:2)
openoffice cracks (Score:1)
Already, two speakers have made wisecracks about OpenOffice.org, tagging it as a bloated memory hog.
I have happier memories of OLS and openoffice: it was at OLS in 2000 that Miguel de Icaza announced, during his keynote, that StarOffice would be opensourced and available at openoffice.org. This got a tremendous round of applause, so Andy Oram need not despair that OLS attendants don't grasp the importance of office suites.
Re:openoffice cracks (Score:2)
I do understand the importance of office suites
Open office takes about 30s to start on my 256Mb Pentium 3 laptop. Sorry, but that's fucking ridiculous.
Re:openoffice cracks (Score:1)
I wasn't trying to say that wisecracks about openoffice being big and slow are invalid. On the contrary, whenever I pitch openoffice to msoffice users, I brace myself for their inevitable "that's way too slow" feedback. The start up speed is definitely an embarassment. I was reacting to the tone of Andy Oram's comment:
"Already, two speakers have made wisecracks about OpenOffice.org, tagging it as a bloated memory hog. I have the suspicion that some atte
LWN Articles (Score:5, Informative)
[LWN subscriber-only content]
Friday was virtualization day at the 2005 Ottawa Linux Symposium; the large room was devoted to that topic all day long. Your editor can only handle so much virtualization at once, and so failed to attend the full set of sessions. Two talks, however, gave a good overview of where a couple of the most important Linux virtualization projects are and what they see in the future.
Xen
A full house turned out to hear Xen hacker Ian Pratt discuss his project. Xen is riding high; the software is cool and getting cooler, the venture money is flowing in, and there is no lack of buzz. Ian's talk, while mostly technical in nature, showed the signs of an up-and-coming business: slick, animated slides, and a good marketing pitch ("virtualization in the enterprise") on why virtualization is a useful thing in the first place. This was worth seeing; it is easy to understand why something like Xen is cool technology, but it can be harder to get a handle on why investors are lining up to throw money at it.
Virtualization is not a particularly new idea. Your editor first experienced it on an IBM mainframe over twenty years ago; we shared files by sending them out our virtual card punch into a co-worker's virtual card reader. Given that the alternative, in that particular time and place, was a real card reader, this looked pretty good. Every now and then things would go weird, and we would have to reboot CMS on our virtual CPU. Not only have things changed little since then, but that was all old stuff even on those days.
In the Linux world, virtualization takes one of three forms. In the "single operating system image mode," as used by the Linux-vserver project (or a simple chroot() setup, for that matter), instances are run within resource containers. Getting strong isolation is hard with this approach. Full virtualization runs an unmodified operating system in a complete virtual machine; systems like VMWare and Qemu work this way. The problem with full virtualization is that it can be hard to do in a way which is both secure and efficient, especially on current x86 hardware. Finally, there is para-virtualization, where the guest operating system kernel is explicitly ported to a virtual machine architecture; both Xen and user-mode Linux are para-virtualized systems.
So why bother with all of this? One is server consolidation: move all of those servers onto fewer actual boxes, with the resulting savings in floor space, power, air conditioning, and hardware maintenance. If you can move virtual machines between physical hosts, you can shift them around to avoid down time; when the disk drive starts to squeal, the administrator can evacuate the virtual systems to working hardware and deal with the problem. Migration also allows workload balancing; it is easier to put more virtual systems on each physical host if they can be shifted around to keep the load on all of those hosts about the same.
One other use for virtualization is security: putting a process within a virtual machine encapsulates it nicely. Even if that process is compromised, there are limits to the damage it can do - as long as it remains trapped within its virtual host. It is also possible to monitor the behavior of the virtual hosts themselves; if one starts doing unusual things, there is a good chance it has been compromised. In this sense, virtualization achieves the same broad goal as SELinux: it puts walls between applications running on the same host. The virtualization approach has the advantage of relative simplicity for situations where all users of a host are to be completely isolated from each other.
Xen, currently, is at version 2.0.6. It provides secure isolation, resource control, quality of service guarantees, live migration of virtual machines, and an execution speed which is "close to native" on the x86 architecture. As a para-virtualization system, Xen requires that the guest kernel be ported to its virtual architecture; ports exist for NetBSD, FreeBSD, Pla
Re:LWN Articles (Score:2, Informative)
Re:LWN Articles (Score:3, Informative)
Of course, such things are freely overlooked here when the publication in question isn't in favour. I don't like it personally, but evidently many are just fine with it.
Too bad I don't have any mod points right now.
Re:LWN Articles (Score:2)
Xen
Your post is very insightful, but nobody is willing to read it - it's way to long.
There is one major disantvantage of Xen: you can't address more than 4 Gig of RAM for the host machine. That is the reason why everyone's (major businesses) going to implement VMware, which is by far not that effective/performant than Xen.
You're obviously talking about the benefits of virtualization, but if you have to implement it in critical environments, you have to realize that there is nothing else than VMwar
Re:LWN Articles (Score:2)
I would have gone but it was a bit pricy. (Score:2)
Linux is used in the development of Intel procs (Score:1, Informative)
The Macintels are developed on Linux
Didn't know about it (Score:1)
Anyone know of othe Linux conferences that will be happening in Canada over the next few months? Would love to know about them.
my OLS writeups (Score:1)
Here's a table of contents for my posts:
Day One [livejournal.com]: 2.6 kernel roadmap, Novell Linux Kernel Debugger, Hot Keys, Video Control, Suspend/Resume, Oh My! -- Recent Advances and Current Challenges in Linux/ACPI, TWIN: An Even Smaller Window System for Even S