Arch Linux User Repository

I use this package, dump, for retrocomputing purposes. Many artifacts contain filesystem dumps which can be extracted ("burst") from those.

# The artifacts start with a SIMH tap file. I use a subdirectory to contain the artifacts.
mkdir burst
cd burst
# rawtap is from https://github.com/simh/simtools
rawtap -e 41bsd_7-10-81.tap
# This is the raw tape image from rawtap which contains the root filesystem dump
file 00002.dat
00002.dat: old-fs dump file (little endian), Volume 1, Level zero, type: tape header,
# create an empty file, 300MB is just approximate, use whatever size you need.
dd if=/dev/zero of=rootfs.ext3 bs=1M count=300
# dumps are restored into file systems so:
mkfs.ext3 rootfs.ext3
mkdir root
# save the name of the loop device in 'dismount-device'
sudo losetup --show --find rootfs.ext3 | tee dismount-device
sudo mount -t ext3 rootfs.ext3 root
cd root
sudo restore xf ../00002.dat
# At this point the root file system from the artifact is under the 'root' directory.
# You can untar usr into root/usr and so on.
# make sure you have the correct tape
file ../00003.dat
../00003.dat: tar archive
tar tf ../00003.dat | head -n2
adm/
adm/acct
# A 4.1BSD distribution is documented as having five tape files
# but some older ones only have three.
cd usr
sudo tar xf ../../00003.dat
cd src
sudo tar xf ../../../00004.dat
# and so on for all the tar file artifacts.
# Once it's extracted, cd to the burst directory
cd ../..
# deactivate the loop device, the name was saved in a step above
dev=$(cat dismount-device)
sudo umount $dev
sudo losetup -d $dev
rm dismount-device

At this point, rootfs.ext3 can be mounted whenever you want to peruse the source code. This is especially useful when you want to compare two different versions to see what changed over time.

diff -rub 4.1BSD-7-10-81/ 4.1BSD-19830510/

A handy script to activate rootfs.ext3

$ cat jumpstart-4.1BSD 
#! /bin/bash

set -ex
sudo losetup --show --find rootfs.ext3 | tee dismount-device
sudo mount -t ext3 rootfs.ext3 root

to stop this thing

$ cat shutdown-4.1BSD
#! /bin/bash

if [ ! -s dismount-device ]; then
    echo you lose
    exit 1
fi

dev=$(cat dismount-device)
sudo umount $dev
sudo losetup -d $dev

So as you can see, this package is useful for more than making backups of Linux.

Great. Thanks for your feedback.

now ok for me. thx.

/bin/ld: main.o:(.bss+0x13c0): multiple definition of `u_spcl'; itime.o:(.bss+0x20): first defined here

Looks like this does not compile under gcc 10, but does if you add CC=gcc-9 to the ./configure environment in PKGBUILD (with gcc9 installed, of course).

Please consider this diff to avoid compiling problems while having the newer openssl-1.1.x installed:

diff --git a/PKGBUILD b/PKGBUILD
index [`9e89206`](https://aur.archlinux.org/cgit/aur.git/commit/?h=dump&id=9e89206)..ff57663 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -21,13 +21,15 @@ arch=('i686' 'x86_64')
 url="<http://dump.sourceforge.net/>"
 license=('BSD')
 depends=('e2fsprogs')
-makedepends=('autoconf' 'automake' 'pkg-config')
+makedepends=('autoconf' 'automake' 'pkg-config' 'openssl-1.0')
 source=("<http://downloads.sourceforge.net/>$pkgname/$pkgname-$pkgver.tar.gz")
 md5sums=('4c463f797e7e8a1112fabf5cbf8e1855')

 build() {
   cd "$srcdir"/$pkgname-$pkgver

+  PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig \
+  CFLAGS+=" -I/usr/include/openssl-1.0" \
   ./configure --prefix=/usr \
     --sysconfdir=/etc \
     --with-manowner=root \

need rebuild

PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig \
CFLAGS+=" -I/usr/include/openssl-1.0" \
LDFLAGS+=" -L/usr/lib/openssl-1.0 -lssl"  \
./configure