ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Tanish Shinde <tanishshinde2006@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Anatomy Of The Linux Kernel
Date: Mon, 17 Jun 2019 09:33:36 -0400	[thread overview]
Message-ID: <20190617133336.GA4358@mit.edu> (raw)
In-Reply-To: <CAFTVhMen6LqB2p8Ptq0CeUWw9hiJDVU6Z_70yMbQLSG2HbJVOQ@mail.gmail.com>

On Sat, Jun 01, 2019 at 11:22:32PM +0530, Tanish Shinde wrote:
> > I have taken the time to develop the framework for my next talk
> >  Structural Decomposition Of The Linux FileSystem #101
> > Please take this talk into consideration and I believe that this is very
> > high level discussion about the Linux Filesystem, and also tell me your
> > thoughts on it its pretty lengthy and incredibly detailed and requesting to
> > reply as soon as possible

Hi Tanish,

Apologies for the delay in responding.  In general, tutorial level
talks are not appropriate for either the Plumbers Conference or Kernel
Summit.

This applies both to your submission, "Building A Docker Engine On A
Custom Linux OS For Raspberry Pi 3" and your proposed talk,
"Structural Decomposition Of The Linux FileSystem".

A description of how Windows uses the C:/ and D:/, and contrasting
this with Linux's use of mounts and a single directory hierarchy, as
well as /bin, /boot, and /dev, is far too basic this conference.
The talks you have submitted appropriate for the Open Source Summit;
perhaps you should consider submitting them to those conferences?

At the Kernel Summit and Linux Plumbers Conference, most of the
attendees who are interested in file systems are people who write and
maintain new file systems in the kernel.  We will also have people who
create the container systems which are used as the basis of systems
like Docker.  Many attendes will have built one (or more!) automated
systems for creating root file systems for embedded systems on
Raspberry Pi's, mobile handsets, automative systems, etc, so a manual
walkthrough of how to install the boot loader, kernel, and root file
system on an image designed to be written onto a SD Card is not going
to be terribly interesting for the conference attendees.

Best regards,

						- Ted

      parent reply	other threads:[~2019-06-17 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  6:09 Theodore Ts'o
2019-06-01  9:02 ` Leon Romanovsky
2019-06-01  9:43   ` Greg KH
     [not found]     ` <CAFTVhMc6cjQko4pMdK0Vq1wOj+Wv+sSgWzwULhVQQF9+AL02JA@mail.gmail.com>
2019-06-01 17:52       ` Tanish Shinde
2019-06-03  4:48         ` Leon Romanovsky
2019-06-17 13:33         ` Theodore Ts'o [this message]

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=20190617133336.GA4358@mit.edu \
    --to=tytso@mit.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tanishshinde2006@gmail.com \
    /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