From: Jay Sulzberger <jays@panix.com>
To: guile-devel@gnu.org
Cc: mentors@gnu.org, rms@gnu.org
Subject: Re: Rename GNU fdisk to GUILE diskutils
Date: Wed, 13 Dec 2017 20:39:22 -0500 (EST) [thread overview]
Message-ID: <Pine.NEB.4.64.1712132008360.17379@panix3.panix.com> (raw)
In-Reply-To: <87609gggj8.fsf@yahoo.it>
On Sat, 9 Dec 2017, Christian Brunello Christian Brunello
<mail.kristian@yahoo.it> wrote:
>
> Hello everyone,
>
> I write because I would like to rename the GNU fdisk
> package.
>
> In the version I am preparing, the program is written in Scheme, using
> Guile. In this release there will be only the fdisk program, but in the
> future I want to add more. So a more generic name would be appropriate.
>
> I discussed this with Richard Stallman, and the volunteers on the
> mentors@gnu.org list. Since the package is based on GUILE, we consider
> using the name "Guile Diskutils".
>
> We wanted to know what you think of this name.
>
> --
> Christian Brunello
I have forgotten when I first used the present program called
"fdisk". I use it only on systems with the Linux kernel and all
*nix utilities being GNU utilities. Recently I use it one day a
week on several systems, mainly to check that I know what drives
are plugged into which computers. So I mainly do
fdisk -l
I am for keeping the name "fdisk" for the new GUILE-LISP POWERED
HYPERDRIVE MANIPULATOR. To me, fdisk feels like a basic standard
utility, like ed^WEmacs. So the name should remain the same even
unto and beyond the day it works by teleporting the drive to
Frolix-8 and asking our friends there to do the work. When fdisk
becomes a small, but always foundational!, part of the new GNU
collection of low level data mungers, its info page should have a
section presenting the Scheme theoretic techniques used to build
all the parts of the package.
oo--JS.
next prev parent reply other threads:[~2017-12-14 1:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 13:46 Rename GNU fdisk to GUILE diskutils Christian Brunello
2017-12-12 18:11 ` Eric Bavier
2017-12-12 21:48 ` David Pirotte
2017-12-12 23:43 ` Christian Brunello
2017-12-13 0:01 ` David Pirotte
2017-12-13 8:34 ` tomas
2017-12-13 23:40 ` Freja Nordsiek
2017-12-14 12:14 ` Christian Brunello
2017-12-13 16:49 ` Stefan Monnier
2017-12-13 23:02 ` Richard Stallman
2017-12-20 13:55 ` Christopher Lemmer Webber
2017-12-23 8:52 ` Christian Brunello
2017-12-12 23:11 ` Hans Åberg
2017-12-12 23:25 ` Christian Brunello
2017-12-13 23:02 ` Richard Stallman
2017-12-14 1:39 ` Jay Sulzberger [this message]
2017-12-14 22:14 ` Richard Stallman
2017-12-15 2:27 ` Nala Ginrut
2017-12-15 22:21 ` Jay Sulzberger
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.NEB.4.64.1712132008360.17379@panix3.panix.com \
--to=jays@panix.com \
--cc=guile-devel@gnu.org \
--cc=mentors@gnu.org \
--cc=rms@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).