[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681261: live-build: please don't leave an empty fstab in chroot

Sorry, forgot to CC the BTS, so I'm resending this mail.

On Thu, Jul 12, 2012 at 05:35:53PM +0200, Daniel Baumann wrote:
> severity 681261 normal
> retitle 681261 update fstab even if non-existent (possibly fstab.d too)
> reassign 681261 partman
> thanks
> On 07/11/2012 09:18 PM, Rui Bernardo wrote:
> > when installing to disk, with live-installer and using a multiple

Just to clarify, when using a multiple schema is when the problem really 
shows up, but even with a "all-in-one" schema, fstab is empty. There 
aren't any aparent problems on boot because initramfs-tools (or 
initscripts) mounts the root filesystem. But still the fstab is empty 
and it will not find swap, for example.

> > partition schema in partman, the presence of an empty fstab in the
> > squashed filesystem breaks the fstab that is created by partman.
> as i said on irc some month ago when you first reported this, this is
> not a bug in live-build, we do not want an fstab on purpose.
> d-i (or partman) do need to handle that properly, ideally by using
> fstab.d as of wheezy anyway.

That would be good. Maybe live-build should also use fstab.d instead of 
overwriting what partman wrote with an empty one by default. It breaks 
any partitioning preseed and any encryption chosen in partman.

If a live-build user wants an empty (or not) fstab he/she can add it in 
the includes.chroot, even using fstab.d, but live-build "forcing" an 
empty fstab if the user don't include one is a problem.

> -- 
> Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
> Email:          daniel.baumann@progress-technologies.net
> Internet:       http://people.progress-technologies.net/~daniel.baumann/

Reply to: