Bug#215544: O: sash -- Stand-alone shell.
Package: wnpp
Severity: normal
The current maintainer of sash, Raul Miller <moth@debian.org>, is
apparently not active anymore. Therefore, I orphan this package now.
If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.
Some information about this package:
Package: sash
Binary: sash
Version: 3.4-8.3
Priority: optional
Section: shells
Maintainer: Raul Miller <moth@debian.org>
Build-Depends: zlib1g-dev (>= 1:1.1.3-19.1), debmake
Architecture: any
Standards-Version: 3.2.1
Format: 1.0
Directory: pool/main/s/sash
Files: 643a47adeab5be325e0bfef5277ff630 559 sash_3.4-8.3.dsc
9c631eb171371b69276ff6692100beb6 49149 sash_3.4.orig.tar.gz
99da0e5df2700a54584c3dc02a1a872d 9234 sash_3.4-8.3.diff.gz
Package: sash
Priority: optional
Section: shells
Installed-Size: 600
Maintainer: Raul Miller <moth@debian.org>
Architecture: i386
Version: 3.4-8.3
Depends: lockfile-progs
Suggests: doc-debian, debconf
Conflicts: fileutils (<<4.0-1)
Filename: pool/main/s/sash/sash_3.4-8.3_i386.deb
Size: 218648
MD5sum: 3a917620222125988bf18c9187705463
Description: Stand-alone shell.
sash serves as an interactive substitute for /bin/sh, for use when
/bin/sh is unusable. It's statically linked, and includes many standard
utilities as builtins (type "help" at the prompt for a reference list).
If you've installed sash before rendering your system unbootable, and
you have some knowledge of how your system is supposed to work, you might
be able to repair your system using init=/bin/sash at the boot prompt.
.
Some people also prefer to have sash available as the shell for a
root account (perhaps an under an alternate name such as sashroot)
Configuration support is included for people who want this.
.
Note: sash is not intended to serve as /bin/sh, and has few of the
interactive features present in bash or ksh. It's designed to be simple
and robust, for people who need to do emergency repair work on a system.
.
Also note: sash doesn't include a built-in fsck -- fsck is too big
and complicated. If you need fsck, you'll have to get at least one
partition or disk working well enough to run fsck. More generally,
sash is but one tool of many (backups, backup recovery tools, emergency
boot disks or partitions, spare parts, testing of disaster plans,
etc.) to help you recover a damaged system.
Justification: No upload since August 2001, several NMUs, maintainer address
bounces.
--
Martin Michlmayr
tbm@cyrius.com
Reply to: