Package: manpages
Version: 4.16-2
Severity: normal

In #847998 we removed the tmpfs(5) manpage because it conflicted with
the initscripts. But now, we have systems that are installed, by
default, without that package, which means we don't have a tmpfs(5)
manpage at all!

That's quite unfortunate, and I believe it should be fixed. In #847998
it was agreed that the conflict should be somehow resolved.

I filed a bug against initscripts (#951596) so that they just remove
their version of the manpage. My argument is that initscripts can use
the normal tmpfs(5) syntax (from fstab, not /etc/default) now so there
doesn't need to be special configuration for that. And if there should
be, I believe it is reasonable that it sits in a different manpage,
since we can definitely use tmpfs without any init system at all: it's
part of the kernel, after all.

(Well, Linux needs *some* init system, but the point I'm making here
is that you can use tmpfs(5) with init=/bin/sh.)

So I'm opening this bug in manpages so we restore this manpage, but it
shouldn't be done until initscripts removes theirs, naturally.

-- System Information:
Debian Release: 10.3
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

manpages depends on no packages.

manpages recommends no packages.

Versions of packages manpages suggests:
ii  man-db [man-browser]  2.8.5-2

-- no debconf information

Reply via email to