public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Kernel choice in IPFire 3.x
Date: Fri, 20 Jan 2012 17:13:45 +0100	[thread overview]
Message-ID: <1327076025.2165.64.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4F1816B4.3000202@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]

Hey,

I think that is quite long, but actually when I was talking to Arne, he
came up with the following idea:

Why name the PAE-kernel kernel-PAE when PAE is only one of the features
it comes with and is the default one. It would be much better to call if
the default kernel. Nothing else.

That would imply that we need to rename the other version, which is a
bit hard to do, because I have not found a simply and cheesy name that
is to the point. Any suggestions?

 -Michael

On Thu, 2012-01-19 at 14:12 +0100, Daniel Weismüller wrote:
> Hi
> 
> Why you just name it "without-PAE"
> 
> Daniel
> 
> Am 19.01.2012 12:46, schrieb Michael Tremer:
> > Hey Daniel,
> >
> > thank you for your reply.
> >
> > Do you have any suggestion for the name of the "default" kernel?
> >
> > I think it is not that bad because that kernel runs by "default" on any
> > i686 box. But there may be better names around.
> >
> > Michael
> >
> > P.S. Make sure you reply to Arne and Ben as well, because they have not
> > subscribed to this list.
> >
> > On Thu, 2012-01-19 at 08:32 +0100, Daniel Weismüller wrote:
> >> Hi!
> >> Good work at all. I think it is easy to understand why it is necessary
> >> to use different kernels.
> >>
> >> Only one point. In my opinion it is a bad choice to name the "i686
> >> non-pae kernel" "default kernel" because it isn't our default kernel for
> >> the i686 architecture.
> >>
> >> Daniel
> >>
> >> Am 18.01.2012 23:12, schrieb Michael Tremer:
> >>> Hello you 2,
> >>>
> >>> I would like you to review the documentation I have written about the
> >>> kernel choice in IPFire 3.x at http://wiki.ipfire.org/devel/kernels.
> >>>
> >>> We should just briefly write down why we decided to do things in this
> >>> way and I want to make sure that I did not get anything wrong or missed
> >>> an important reason.
> >>>
> >>>    -Michael
> >>>
> >>> P.S. Please make sure to reply to the list as well.
> >>>
> >>> _______________________________________________
> >>> Documentation mailing list
> >>> Documentation(a)lists.ipfire.org
> >>> http://lists.ipfire.org/mailman/listinfo/documentation
> >> _______________________________________________
> >> Documentation mailing list
> >> Documentation(a)lists.ipfire.org
> >> http://lists.ipfire.org/mailman/listinfo/documentation


  reply	other threads:[~2012-01-20 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 22:12 Michael Tremer
2012-01-19  7:32 ` Daniel Weismüller
2012-01-19 11:46   ` Michael Tremer
2012-01-19 13:12     ` Daniel Weismüller
2012-01-20 16:13       ` Michael Tremer [this message]
2012-01-20 16:22         ` Ben Schweikert
2012-01-20 16:38           ` Michael Tremer
2012-01-21 13:36             ` Michael Tremer
     [not found] <CAO6L5t8LWpMhZfeyfBu-HttU5g6OoB_6t5Mxvzp89sDxDNHmOA@mail.gmail.com>
2012-01-23 15:31 ` Michael Tremer

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=1327076025.2165.64.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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