From: L A Walsh <lkml@tlinx.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.33-rc1
Date: Sun, 30 Sep 2018 16:33:14 -0700 [thread overview]
Message-ID: <5BB15D3A.8040507@tlinx.org> (raw)
In-Reply-To: <20180925104701.y2gwtwe2bquynap2@ws.net.home>
On 9/25/2018 3:47 AM, Karel Zak wrote:
> The commands mount and umount
---
I note that umount has a static option umount.static, but I don't see
the same for mount (i.e. mount.static).
It seems the main benefit of static is to ensure the command will run
if there is a problem with runtime-linking or if libraries are missing.
Examples might be a root FS that may have significantly reduced
content but enough to do FS restore operations, emergency repairs and
load kernel modules that will allow one to bring up rest of the system.
Basic functionality would include ability to mount file systems and
ideally format, manage partitions, and restore file systems from
backups.
Some utilites necessary to do such tasks are outside the scope of
util-linux, but at least the ability to mount/umount a file system,
fdisk and partition management. Could it be ensured that one can 'mount'
disks under adverse conditions, at the very least, so that umount.static
would make sense?
> The command rename(1) provides a new command line option --interactive to ask
> before overwriting.
>
---
How does rename compare with 'mmv'? I note that in the manpage "SEE
ALSO" section, 'mv' is listed, (not quite sure why?), but not a more
related tool
like 'mmv'.
next prev parent reply other threads:[~2018-10-01 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 10:47 [ANNOUNCE] util-linux v2.33-rc1 Karel Zak
2018-09-30 23:33 ` L A Walsh [this message]
2018-10-02 10:14 ` Karel Zak
2018-10-06 19:25 ` L A Walsh
2018-10-07 14:57 ` Bernhard Voelker
2018-10-07 16:58 ` L A Walsh
2018-10-08 7:30 ` static linking working w/gnu? (was Re: [ANNOUNCE] util-linux v2.33-rc1) L A Walsh
2018-10-08 9:09 ` Karel Zak
2018-10-08 12:43 ` L A Walsh
2018-10-16 0:48 ` L A Walsh
2018-10-04 22:11 ` [ANNOUNCE] util-linux v2.33-rc1 Ruediger Meier
2018-10-04 22:11 ` Ruediger Meier
2018-10-05 9:37 ` Karel Zak
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=5BB15D3A.8040507@tlinx.org \
--to=lkml@tlinx.org \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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.
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).