Re-write 32bit chroot daemon in systemd service format?

Question

I followed the Arch wiki instructions quite successfully and have been using the daemon script to use a 32bit chroot. I just switched over fully to systemd (at least I think so) and no longer have the ability to start it since rc.conf no longer exists in the 64bit system (and gets copied in the 32bit chroot daemon script).
Systemd is quite foreign and I find it a bit overwhelming at the moment, not having had time to digest it yet -- I was sort of forced in due to a recent upgrade.
In any case, are there suggestions of how to re-write this in systemd language and enable as a service?
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
# Add '/var/run /var/lib/dbus' to the list to enable pulseaudio.
dirs=(/dev /dev/pts /dev/shm /tmp /home)
case $1 in
start)
stat_busy "Starting Arch32 chroot"
for d in "${dirs[@]}"; do
mount -o bind $d /opt/arch32$d
done
mount -t proc none /opt/arch32/proc
mount -t sysfs none /opt/arch32/sys
add_daemon arch32
stat_done
stop)
stat_busy "Stopping Arch32 chroot"
for (( i = ${#dirs[@]} - 1; i >= 0; i-- )); do
umount "/opt/arch32${dirs[i]}"
done
umount /opt/arch32/{proc,sys}
rm_daemon arch32
stat_done
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
It looks like most of it is just bash code, but things like stat_busy and rm_daemon are no longer commands on my system (perhaps provided by initscripts or sysvinit?).
I can add this to the wiki page for other services once I have it figured out, as I'm guessing some others use it and will stumble into the same issue. I don't know what stat_done and others do; like I said, most of it would just be storing this somewhere and having systemd call it on boot, but I don't want to break something by missing an important step because I don't know any better (properly unmounting a drive on service shutdown, for instance).
Thanks for any suggestions/assistance.

Answer 1

jwhendy wrote:
Do you think that would affect my Lotus Notes issue? After following the script commands manually, here is the relevant info:
$ mount
dev on /opt/arch32/dev type devtmpfs (rw,nosuid,relatime,size=1986024k,nr_inodes=496506,mode=755)
devpts on /opt/arch32/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /opt/arch32/dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /opt/arch32/tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/mapper/root on /opt/arch32/home type ext4 (rw,noatime,commit=600,data=ordered)
none on /opt/arch32/proc type proc (rw,relatime)
none on /opt/arch32/sys type sysfs (rw,relatime)
It looks like I hit the necessary files?
The one that stands out is /dev/mapper/root on /opt/arch32/home, but that's what results with:
$ sudo mount -o bind /home /opt/arch32/home
I'm a bit puzzled about that one... Doing `ls /opt/arch32/home` after mounting, however, does show my user folder in there, and `ls -l` shows they're my permissions (jwhendy:users).
I do appreciate the help!
The mount bind for home is actually the way it is supposed to be.  This is the intended behaviour.  It gives you verbatim access to whatever it is bound to.
Are you actually in the chroot when you start Lotus Notes?  Even though the host architecture shouldn't matter, running 32-bit applications in the chroot should behave correctly.  In the past 32-bit chroot's there was another bash binary called arch32 that did your chroot /opt/arch32, but you can still do that manually.
Last edited by nomorewindows (2012-11-02 20:03:54)