zsh-workers
 help / color / mirror / code / Atom feed
From: Dan Nelson <dnelson@allantgroup.com>
To: zsh-workers@sunsite.dk
Subject: Re: Notes on zsh, zsh/files and recovery
Date: Sun, 19 Oct 2008 01:39:24 -0500	[thread overview]
Message-ID: <20081019063924.GO99270@dan.emsphone.com> (raw)
In-Reply-To: <20081018204515.GA1642@redoubt.spodhuis.org>

In the last episode (Oct 18), Phil Pennock said:
> Managed to hose my box by trying to be too clever while rebuilding.
> Luckily, had zsh as root at the time.  In the end, didn't help fix
> it; once you've hosed /libexec/ld-elf.so.1 with a version that's for
> a different architecture to the kernel, you're hosed.  But it's an
> interesting exercise, trying to recover without making use of exec()
> (as opposed to the more usual fork() limitation).

You mention FreeBSD later, so if something similar happens again, you
should be able to use the statically-linked binaries in /rescue to
recover from most shared-library problems, especially if you've got
another system you can NFS-mount to copy files from.  Surprisingly, ftp
isn't in there, so if you need executables or libraries from
ftp.freebsd.org you'd have to ftp them from another box and copy them
via USB drive or something similar.
 
> There does not appear to be a zls() ?  I hacked one together using
> zsh/stat and ... it's rather slow.  I'm tempted to build up a closer
> emulation of ls(1) with a few useful options and contribute it as a
> standard function.  It will be truly slow, but occasionally useful.

In emergencies, I have used this as an ls replacement :)

ls() { echo ${@:-*} }

-- 
	Dan Nelson
	dnelson@allantgroup.com


  parent reply	other threads:[~2008-10-19  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 20:45 Phil Pennock
2008-10-18 20:56 ` Mikael Magnusson
2008-10-19  6:39 ` Dan Nelson [this message]
2008-10-20  0:28   ` Phil Pennock
2008-10-20 15:09     ` Bart Schaefer

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=20081019063924.GO99270@dan.emsphone.com \
    --to=dnelson@allantgroup.com \
    --cc=zsh-workers@sunsite.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).