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

Bug#1031836: nvi: refuses to start with read-only rootfs (/var/tmp)



Control: severity 1031836 wishlist

Hi,

在 2023-02-23星期四的 23:31 +0100,наб写道:
> Package: nvi
> Version: 1.81.6-16
> Severity: normal
> 
> Dear Maintainer,
> 
> -- >8 --
> # vi /etc/snmp/snmpd.conf
> ex/vi: Error: /var/tmp/vi.recover: Read-only file system
> ex/vi: Modifications not recoverable if the session fails
> ex/vi: Error: /var/tmp/vi.recover/vi.pL7kw0: No such file or directory
> -- >8 --
> 
> This is fatal. /No one/ can edit /anything/, it seems,
> until /var/tmp is made writable (be it by remounting / rw,
> or, indeed mounting tmpfs on /var/tmp).
> 
> This should be a non-fatal warning.

According to FHS and Linux common practice [1][2], /var/tmp/ should be
world-writable in a sane environment. Supporting a non-standard environment
should be in wishlist. You are welcome to provide a patch to Debian or
forward the patch to upstream. Please note that the upstream of nvi may not
be active now [3], but giving it a try is always harmless.

Thanks,
Boyuan Yang


[1] https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html
[2]
https://www.redhat.com/en/blog/polyinstantiating-tmp-and-vartmp-directories
[3] likely to be https://repo.or.cz/nvi.git

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: