On Tue, Aug 08, 2017 at 05:12:03PM -0500, Rob Landley wrote:
> If your rootfs has a size= in /proc/mounts it's tmpfs, ala:
>
> rootfs / rootfs rw,size=126564k,nr_inodes=31641 0 0
You're right, I have it and thought about it. Anyway the point is that
it works transparently for me. Apparently
On Tue, Aug 08, 2017 at 05:12:03PM -0500, Rob Landley wrote:
> If your rootfs has a size= in /proc/mounts it's tmpfs, ala:
>
> rootfs / rootfs rw,size=126564k,nr_inodes=31641 0 0
You're right, I have it and thought about it. Anyway the point is that
it works transparently for me. Apparently
On 08/08/2017 07:04 AM, Willy Tarreau wrote:
> 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
On 08/08/2017 07:04 AM, Willy Tarreau wrote:
> 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
On Tue, Aug 08, 2017 at 03:18:19PM +0200, Thomas Meyer wrote:
> On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote:
> > Hi Thomas,
> >
> > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote:
> > > Hi,
> > >
> > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break
On Tue, Aug 08, 2017 at 03:18:19PM +0200, Thomas Meyer wrote:
> On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote:
> > Hi Thomas,
> >
> > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote:
> > > Hi,
> > >
> > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break
On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote:
> 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
On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote:
> 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
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
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
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?
with kind regards
thomas
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?
with kind regards
thomas
12 matches
Mail list logo