zsh-users
 help / color / mirror / code / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-users@zsh.org
Subject: Re: Bug/Request: _umountable should not depend on /etc/mtab
Date: Fri, 16 Oct 2020 16:11:10 +0200	[thread overview]
Message-ID: <CADYdroMUhw9zEOxuOUm6XHMuA4cKk0EUEJnH==1U8+5nyKDSRg@mail.gmail.com> (raw)
In-Reply-To: <58433fbc-e91c-4ed5-8f36-104a1b6a1ee9@www.fastmail.com>

Am Fr., 16. Okt. 2020 um 15:35 Uhr schrieb Daniel Shahaf
<d.s@daniel.shahaf.name>:
>
> Norbert Lange wrote on Fri, 16 Oct 2020 10:14 +00:00:
> > Hello,
> >
> > On Linux, /etc/mtab is ancient history, please use /proc/self/mounts.
> > Atleast the _unmountable function is affected.
> > (its easy to add an compatibility symlink, but this should not be necessary)
>
> Can we just s#/etc/mtab#/proc/self/mounts#g?  I.e., what Linux systems
> _don't_ have /proc/self/mounts?  (New systems with custom kernel
> configs?  Old systems?  _How_ old?)
>
> Failing that, the code will have to use /proc/self/mounts if it exists
> and /etc/mtab otherwise.

Hi,

/proc/self/mounts has been available since Linux 2.4.19, released in 2002.
Given how likely that is to run on current hardware I'd say, just sed away.

/proc/self/mounts is itself superseded by /proc/self/mountinfo,
which contains more info but has a different format.

https://man7.org/linux/man-pages/man5/proc.5.html

Norbert


  reply	other threads:[~2020-10-16 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 10:14 Norbert Lange
2020-10-16 13:35 ` Daniel Shahaf
2020-10-16 14:11   ` Norbert Lange [this message]
2020-10-16 14:33     ` Daniel Shahaf
  -- strict thread matches above, loose matches on Subject: below --
2020-10-02  9:29 Norbert Lange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADYdroMUhw9zEOxuOUm6XHMuA4cKk0EUEJnH==1U8+5nyKDSRg@mail.gmail.com' \
    --to=nolange79@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).