Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Rob Landley
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Rob Landley
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Willy Tarreau
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

INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
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

INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
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