From: Nick <nick@linicks.net>
To: Otto Wyss <otto.wyss@orpatec.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OSDL and the Linux kernel community
Date: Sat, 28 Jan 2006 17:10:31 +0000 [thread overview]
Message-ID: <7c3341450601280910h5f681ae3g@mail.gmail.com> (raw)
In-Reply-To: <43DB8EC3.5040907@orpatec.ch>
On 28/01/06, Otto Wyss <otto.wyss@orpatec.ch> wrote:
> I've just read about Greg Kroah-Hartman (one of the 17 kernel
> developers) proposal about what OSDL could do to improve the kernel
> work. As a none-kernel developer I think it's important to look closer
> at some of the issues.
Of course, you can do what I do at work - promote GNU/Linux in _every_
conversation with the users (no matter waht the topic).
Only this week I recovered 1.2GB of pictures from a users home
computer that die running eXtra Problems.
Using Knoppix and a USB stick with the bad drive mounted on hdb (ok,
took 6 'runs' to recover all data) , he was WELL impressed (his wife
even more so...) and started asking questions...
Nick
next prev parent reply other threads:[~2006-01-28 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 15:33 OSDL and the Linux kernel community Otto Wyss
2006-01-28 17:10 ` Nick [this message]
2006-01-28 21:16 ` Chase Venters
2006-01-28 22:51 ` Greg KH
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=7c3341450601280910h5f681ae3g@mail.gmail.com \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@orpatec.ch \
/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