zsh-workers
 help / color / mirror / code / Atom feed
From: James Antill <james@and.org>
To: Zefram <zefram@fysh.org>
Cc: jimkirk@uwyo.edu (James Kirkpatrick),  zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: chown and chgrp in files module
Date: 09 Dec 1999 18:40:43 -0500	[thread overview]
Message-ID: <nnso1bznr8.fsf@code.and.org> (raw)
In-Reply-To: Zefram's message of "Thu, 9 Dec 1999 17:41:23 +0000 (GMT)"

Zefram <zefram@fysh.org> writes:

> James Kirkpatrick wrote:
> 
> >This does not seem to be the sort of thing that should be built in to a
> >shell, any more than rm, ls, find, or a C compiler :-)
> 
> It's very useful to have these things built into a statically-linked
> system administration shell.  (That's where the request for a builtin
> chown originated.)  In addition to the utilities I listed above, we have
> a `stat' module that effectively makes possible a full implementation
> of ls as a shell function, and zsh globbing with glob qualifiers very
> nearly makes find redundant.

 Which begs the question, who's working on the C compiler ?:)

ObZsh: Would it be possible to have a statically linked sys-admin
shell built as part of the build process. Then you could literally
just have it[1] on a floppy and boot Linux with init=/bin/zsh_admin.

[1] Ignoreing the kernel and a _very_ small root fs (ok I guess you
probably want vi and fsck too ... but not much more).

-- 
James Antill -- james@and.org
I am always an optimist, but frankly there is no hope.
   -Hosni Mubarek


  parent reply	other threads:[~1999-12-10 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09 16:02 zefram
1999-12-09 17:20 ` James Kirkpatrick
1999-12-09 17:41   ` Zefram
1999-12-09 18:19     ` James Kirkpatrick
1999-12-09 23:40     ` James Antill [this message]
1999-12-13 12:10       ` Zefram
1999-12-10 21:43     ` Clint Adams

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=nnso1bznr8.fsf@code.and.org \
    --to=james@and.org \
    --cc=jimkirk@uwyo.edu \
    --cc=zefram@fysh.org \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).