netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andy Johnson" <johnsonzjo@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: gdt@gdt.id.au, netdev@vger.kernel.org
Subject: Re: Netconf at conf.au 2008?
Date: Mon, 14 Jan 2008 10:34:44 +0200	[thread overview]
Message-ID: <147a89290801140034r77233dcdu4f49786286ca327d@mail.gmail.com> (raw)
In-Reply-To: <20080113.180802.243708508.davem@davemloft.net>

Hello,
Sorry to hear that; I believe many would want to attend netconf in case
it was a part of LCA08. I must add that I followed some of the presentations
slides of netconf from recent years and it seemed very interesting and
very advanced.
I also watched the "Linux IPSEC Scaling" video (available on the internet)
from  LCA 2007 and found it really interesting . (I don't think that there is
any video from netconf conferences from recent years).
I wish that in LCA09 things will be different.


(And of course I did not mean any netconf stuff from martin krafft,
which I already knew before)
Regards,
Andy




On Jan 14, 2008 4:08 AM, David Miller <davem@davemloft.net> wrote:
> From: Glen Turner <gdt@gdt.id.au>
> Date: Mon, 14 Jan 2008 01:23:45 +1030
>
> >
> > On Sat, 2008-01-12 at 08:52 +0200, Andy Johnson wrote:
> > > I saw somewhere (maybe in this mailing list a while ago) that there
> > > might be a  Linux Kernel Developers' Netconf conference  at conf.au
> > > 2008.
> > >
> > > Does anyone here know if  such a thing is planned ?
> >
> > I don't know.
>
> We wanted to do a netconf in Sydney right before LCA08, but an unnamed
> company with a multi billion dollar market capitalization that uses
> Linux networking technology on thousands upon thounsands of their
> servers didn't want to pony up for some funding to cover airfare and
> hotel expenses for several of the attendees.  They wanted to provide
> nothing more than a conference room and then get their names in bright
> lights so they could say they "sponsored" netconf.
>
> So, no, there will be no netconf at LCA08.  But many of us will be
> there anyways and chatting in any event :-)
>
> Thanks for the offer for the network pipe.  I'm not interested
> personally as I like to relax during the conference not hack actively
> on anything too seriously.  I'm there to present, keep up semi
> regularly with my email, and chat with folks.
>
> Now, if this were available outside of the conference so that we could
> play with it remotely from where we work, that's more interesting.
>

  reply	other threads:[~2008-01-14  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12  6:52 Netconf at conf.au 2008? Andy Johnson
2008-01-13 14:53 ` Glen Turner
2008-01-14  2:08   ` David Miller
2008-01-14  8:34     ` Andy Johnson [this message]
2008-01-14 11:01     ` Glen Turner
2008-01-14 11:57       ` David Miller
2008-01-13 18:17 ` martin f krafft
2008-01-14  2:12   ` David Miller
2008-01-14 10:13     ` martin f. krafft
2008-01-14 11:06   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-14 16:39     ` martin f. krafft

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=147a89290801140034r77233dcdu4f49786286ca327d@mail.gmail.com \
    --to=johnsonzjo@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gdt@gdt.id.au \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).