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

Bug#830829: marked as done (release-notes: Document that late-mounting /usr is not supported)

Your message dated Sun, 05 Feb 2017 14:14:00 +0000
with message-id <c66f0b15-c7ea-1f25-dd94-65c660c2a50b@thykier.net>
and subject line Re: Bug#830829: release-notes: Document that late-mounting /usr is not supported
has caused the Debian Bug report #830829,
regarding release-notes: Document that late-mounting /usr is not supported
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
830829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830829
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal

It has been a long time since late-mounting /usr (ie, using only tools
in /) has been actually supported. In stretch, all initramfs generators
mount /usr if it is a separate mount, so that init receives both / and
/usr mounted.

Problems can occur if /usr is not pre-mounted due to:

1. Programs used during early boot require libraries or other files in
   /usr. (Example, #829127)
2. Udev rules might be invoked very early in the boot process, causing
   programs from /usr to be executed. (Example udev rules,
   90-alsa-restore.rules, 63-md-raid-arrays.rules, 39-usbmuxd.rules).

What does this mean for users? It means that if (1) you have /usr on its
own partition, and (2) you do not use an initramfs; then you should
start using one. All of the debian-provided initramfs generators will
generate a suitable one.

The release notes should document this requirement.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Tue, 22 Nov 2016 21:08:12 -0300 Felipe Sateler <fsateler@debian.org>
wrote:
> On 11 July 2016 at 19:53, Felipe Sateler <fsateler@debian.org> wrote:
> > Package: release-notes
> > Severity: normal
> >
> > [...]
> 
> Please find attached a patch doing so. I put this in the issues page,
> but I'm not sure where on that page it should go, so I put it first.
> 
> 
> 
> -- 
> 
> Saludos,
> Felipe Sateler

Thanks, the patch has been applied with a follow up comment to make a
more visible note about who is affected by this.

Thanks,
~Niels

--- End Message ---
Reply to: