Date: Sat, 1 Dec 2018 07:36:01 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Ian Lepore <ian@freebsd.org>, Masachika ISHIZUKA <ish@amail.plala.or.jp>, hackers@freebsd.org Subject: Re: How to use trim command ? Message-ID: <f0b6c70d-0184-b4c0-30bc-68f318c52d57@grosbein.net> In-Reply-To: <1543622218.1860.169.camel@freebsd.org> References: <20181201.011411.2100982142219259108.ish@amail.plala.or.jp> <7e69211c-6ffb-6155-b17a-a845c0b3586d@grosbein.net> <1543622218.1860.169.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
01.12.2018 6:56, Ian Lepore wrote: > And therein lies yet another reason why trim is such a horrible name > for this tool: nothing about the word trim implies destroying live > useful information. In idiomatic English, the word drips with overtones > of removing only the unneeded excess from something. That's because it defaults to dry run and its manual pages emphasizes data imminent destruction several times, in bold. newfs destroys data too, cat > /dev/da0 does this too, add the name "dd" itself does not imply data destruction. Can you invent better name? > Truly, dd (with its 30+ years of association of being THE tool that > operates on disk devices or specified sub-ranges of blocks within them) > is the place for such functionality. In fact, I like both. Sometimes it's handy to use dd while dealing with zero blocks inside an image (or /dev/zero) written to single device file. And sometimes it may be useful to be able to "trim /dev/da0 /dev/ada0" with one call.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f0b6c70d-0184-b4c0-30bc-68f318c52d57>