sash 3.8-5.1 source package in Ubuntu

Changelog

sash (3.8-5.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Move sash to /usr/bin/. (Closes: #1073672)
  * Remove the debconfiscation about the sashroot account, which has
    not been created anymore since sash 3.7-8 released in 2008.
    (Closes: #913933, #1050110, #903861)

 -- Marco d'Itri <email address hidden>  Sun, 07 Jul 2024 17:25:41 +0200

Upload details

Uploaded by:
Tollef Fog Heen
Uploaded to:
Sid
Original maintainer:
Tollef Fog Heen
Architectures:
any
Section:
shells
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
sash_3.8-5.1.dsc 1.2 KiB 7d05c8d7d92ae061011054027396f3b483a6f368ceee6776bb46bfdc2bae9357
sash_3.8.orig.tar.gz 51.8 KiB 13c4f9a911526949096bf543c21a41149e6b037061193b15ba6b707eea7b6579
sash_3.8-5.1.debian.tar.xz 15.2 KiB 83c41b3c09b6a18c3c6ef335656a45ed4122516cbc2c821206b0bb919777e6e4

Available diffs

No changes file available.

Binary packages built by this source

sash: Stand-alone statically linked 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.

sash-dbgsym: debug symbols for sash