Dan Langille | 11 Jan 13:47 2011

BSDCan 2011 - call for papers - reminder

A reminder about BSDCan 2011; the deadline is 19 January 2011.

BSDCan 2011 will be held 13-14 May, 2011 in Ottawa at the University of
Ottawa. It will be preceded by two days of tutorials on 11-12 May.

NOTE: This will be Fri/Sat with tutorials on Wed/Thu.

We are now accepting proposals for talks.

The talks should be designed with a very strong technical content bias.
Proposals of a business development or marketing nature are not
appropriate for this venue.

If you are doing something interesting with a BSD operating system,
please submit a proposal. Whether you are developing a very complex
system using BSD as the foundation, or helping others and have a story
to tell about how BSD played a role, we want to hear about your
experience.  People using BSD as a platform for research are also
encouraged to submit a proposal. Possible topics include:

* How we manage a giant installation with respect to handling spam.
* and/or sysadmin.
* and/or networking.

 From the BSDCan website, the Archives section will allow you to review
the wide variety of past BSDCan presentations as further examples.

Both users and developers are encouraged to share their experiences.

The schedule is:
(Continue reading)

Hubert Feyrer | 11 Jan 19:37 2011
Picon

NYCBSDCon 2010 Final (fwd)


Nice!

  - Hubert

---------- Forwarded message ----------
Date: Tue, 11 Jan 2011 11:08:29 -0500
From: George Rosamond <george <at> ceetonetechnology.com>
To: NYCBUG Admin <admin <at> nycbug.org>
Subject: NYCBSDCon 2010 Final

Spread the word . . .

The organizers of NYCBSDCon 2010 are proud to announce the final closing of the 
books for the November conference at Cooper Union.

The profits are being evenly distributed among the four BSD projects--DragonFly 
BSD, FreeBSD, NetBSD and OpenBSD--with each check totaling $3600.  Most of the 
projects have already received their checks.

This is an enormous accomplishment for an open source conference, and signifies 
the commitment of the broad range of organizers from the New York City *BSD 
User Group and beyond.

The conference, the fourth one held since 2005, attracted a wide array of 
attendees, in addition to generous sponsors including About.com, New York 
Internet, Isilon Systems, Marvell and iXsystems.

The fiscal backing of BSD Fund, a 501(c)(3) organization, provided accounting 
transparency to the conference.
(Continue reading)

Matthew Mondor | 14 Jan 06:51 2011
Picon

NetBSD's reliability [Was: raidframe in netbsd-5?]

On Thu, 13 Jan 2011 12:06:12 -0500
Greg Troxel <gdt <at> ir.bbn.com> wrote:

> And a hat tip to releng <at> ; it's really impressive that this is the first
> time in probably 6 years when I was not comfortable to just "update
> along stable branch and reboot, no worries", and even this is very minor
> and apparently an odd case.  I'll go read the diff when I have a chance.

I concur, the stability and reliability of NetBSD (other than its
versatility) is a major reason I've kept with it, and there are some
systems which are still running which I upgraded from source regularily
over the years, two of them old enough to have started with NetBSD 1.6,
most of them now tracking the netbsd-5 branch and now running NetBSD
5.1_STABLE.

Most of those systems have been upgraded remotely via SSH using NFS or
a copy of the re-built source tree (built using a dedicated host),
after testing the procedure on a local box running the same NetBSD
version.  I've also often moved the software/data around to new
hardware instead of reinstalling, for systems I have physical access
to.  The binary compatibility for older releases also served me well
until the packaged and custom software could also be upgraded or
rebuilt, and for booting+testing kernels before userland upgrades.

Since I started using NetBSD (in the 1.5 days, comming from Linux and
exploring alternatives) I could say that I've seen very few upgrade
glinches; off the top of my head I can now remember three, one related
to a cgd configuration bug, one a postinstall script bug missing a pf
related group, and a PAM and /etc/login.conf related problem, which
have been promptly fixed.
(Continue reading)

Magnus Eriksson | 25 Jan 06:25 2011

Re: NetBSD's reliability

On Fri, 14 Jan 2011, Matthew Mondor wrote:

> (I hope you don't mind me CCing netbsd-advocacy :)

Whatever works to get some traffic on the -advocacy list.  It could use 
some stirring up so it doesn't freeze solid.  :-)

But it's funny; I haven't kept up with recent developments at all for the 
last year or so, and only a few days ago started browsing the mailing list 
archives to see what has happened lately.  What surprised me was seeing 
several people, and at least two new-to-me users saying the same thing: 
"NetBSD is so stable and nice, thanks guys".

Not something I remember happening a lot previously.  Of course, it could 
be from my "compressed" reading that it stood out this time...

It's still as quiet as ever on this list though, so the next person who 
says anything like that will be nudged to forward or cc: here too.

> I concur, the stability and reliability of NetBSD (other than its
> versatility) is a major reason I've kept with it, and there are some
> systems which are still running which I upgraded from source regularily
> over the years, two of them old enough to have started with NetBSD 1.6,
> most of them now tracking the netbsd-5 branch and now running NetBSD
> 5.1_STABLE.

Can I say "me too"?  Even right down to the bit about starting with 1.6 
and being on netbsd-5 now; actually on the system I'm typing this on.

The only real, severe, issues I have had have been with USB in the past -- 
(Continue reading)


Gmane