FOSSLC is a non-profit organization that specializes in technology and know-how to record conferences with excellent quality. Click on the icons below to view great videos from communities we are actively involved with:

 

Sysadmin

Content related to system administration.

Redefining virtualization with live-cloning

in FSOSS, FSOSS2010, Sysadmin, Linux, Programming
Linux

Location

Toronto, ON
Canada
43° 39' 9" N, 79° 22' 54.0012" W
See map: Google Maps

We will demonstrate and present the system administration and performance advantages that can be delivered by the GridCentric Copper virtualization platform.

This will include demonstrations of autoconfigured virtual clusters implementing a wide variety of distributed applications from grid queueing to distributed databases to load-balanced webservers.

Demonstration will also include dynamic, instant resizing of virtual clusters by live-cloning new auto-configured virtual machines in seconds, enabling distributed applications to dynamically scale from one virtual machine to many in a few seconds.

Event: 
FSOSS
Speaker: 
Kannan Vijayan
Vivek Lakshmanan

The NetBSD Way

in BSD, Community, NetBSD, Security, Sysadmin, BSD, Misc
Speaker: 
David Maxwell
Event: 
Summercamp2010
Abstract: 

The origins of BSD and Open Source predate the modern Linux renaissance by a decade and a half, and BSD derived codebases are still going strong. What makes a BSD community different from a Linux community? What technological decisions are given more priority in the BSD world? Why should you care, and why should you use BSD? Come and hear a new perspective. The first BSD Unix-derivative operating system was developed in 1977. Shared as Open Source from the beginning, it provided many people's first exposure to the Open Source concept - especially through its use as the basis for the original SunOS, or the reuse of its TCP/IP stack on widely varied systems (including MS Wi ndows). More recently, whole generations of Open Source developers have grown familiar with Linux as an operating system and community structure, and they've had limited, or no, exposure to BSD. The two cultures have similarities, but also many differences in their approach to community building, code maintenance, design and development, and project man agement. Many OSCON conference attendees may only have exposure to The Linux Way. Come and hear about The BSD Way, and you'll find out why BSD is still going strong, the benefits it can offer you as a user or as a developer, and why us BSD folks don't just drop it all and contribute to Linux instead.

Level: 
Beginner
Time: 
2010-05-31T16:36

Journaled Soft-Updates

in BSDCan, BSDCan2010, Programming, Sysadmin, BSD

Location

University of Ottawa Ottawa, ON
Canada
45° 24' 41.6592" N, 75° 41' 53.4984" W
See map: Google Maps

Adding "journaling lite'' to soft updates and its incorporation into the FreeBSD fast filesystem
BlueCloth error

Because soft updates prevent most inconsistencies, the journaling need only deal with tracking those inconsistencies that soft updates fails to address. Specifically, the journal contains the information needed to recover the block and inode resources that have been freed but whose freed status failed to make it to disk before a system failure. After a crash, a variant of the venerable fsck program runs through the journal to identify and free the lost resources. Only if a corruption of the log is detected is it necessary to run background fsck. The journal is tiny, 16Mb is usually enough independent of filesystem size. Although journal processing needs to be done before restarting, the processing time is typically just a few seconds and in the worst case a minute. It is not necessary to build a new filesystem to use soft-updates journalling. The addition or deletion of soft-updates journaling to existing FreeBSD fast filesystems is done using the tunefs program.

Event: 
BSDCan2010
Speaker: 
Kirk McKusick
05 Apr

Criteria to decide between svn, git, and others

Posted by aross in Community, Git, How To, Programming, Sysadmin, svn, Code repositories, Programming
Git

If someone asked you which code repository your company/team should use, how would you answer? How do you decide something like this?

It's comfortable to go with what you know already. On one hand, training costs and migration is expensive. On the other hand, you might be missing an opportunity to move to a better tool that saves time, energy, and enables scenarios you cannot do today that make you more competitive. This article is a first draft of writing a useful guide to choosing between open source code repositories.