From: Willy Tarreau <w@1wt.eu>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: rob@landley.net, linux-kernel@vger.kernel.org
Subject: Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?
Date: Tue, 8 Aug 2017 14:04:42 +0200 [thread overview]
Message-ID: <20170808120442.GE27367@1wt.eu> (raw)
In-Reply-To: <20170808114625.GA13532@localhost.localdomain>
Hi Thomas,
On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote:
> Hi,
>
> did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel
> build with an included ramdisk?
>
> As fas as I understand you must expliclity add rootfstype=ramfs to the kernel
> command line to boot from the included ramfsdisk?
>
> bug or feature?
Strange, I'm running my kernels with the modules packaged inside the initramfs
and never met this problem even after this commit (my 4.9 kernels are still
packaged this way and run fine). And yes, I do have TMPFS enabled. I can't
tell whether tmpfs or ramfs was used however given that at this level I don't
have all the tools available to report the FS type (and proc says "rootfs").
Are you sure you're not missing anything ?
Willy
next prev parent reply other threads:[~2017-08-08 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 11:46 INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53? Thomas Meyer
2017-08-08 12:04 ` Willy Tarreau [this message]
2017-08-08 13:18 ` Thomas Meyer
2017-08-08 15:40 ` Willy Tarreau
2017-08-08 22:12 ` Rob Landley
2017-08-09 3:30 ` Willy Tarreau
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=20170808120442.GE27367@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=thomas@m3y3r.de \
/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