Hi,
Le 2013-05-12 17:03, intrigeri a écrit :
> Hi quidame,
>
> quidame@??? wrote (25 Mar 2013 12:00:11 GMT) :
>> 2. Get bilibop-common and bilibop-udev packages:
>
> I've tried to build an ISO with bilibop-udev installed.
>
> Unfortunately, bilibop-udev.postinst fails for me because it seems to
> require /proc/mounts to be mounted:
>
> Setting up bilibop-udev (0.4.10~quidame) ...
> df: Warning: cannot read table of mounted file systems: No such
> file or directory
> grep: /proc/mounts: No such file or directory
> dpkg: error processing bilibop-udev (--configure):
> subprocess installed post-installation script returned error exit
> status 1
> Errors were encountered while processing:
> bilibop-udev
>
> ... which is not the case in the chroot that live-build uses to build
> our ISO.
>
> Given we don't care at all about the work that this postinst does
> (triggering udev rules on the current boot disk) in the context of
> Tails, what do you think could be a fine way to make this step be
> skipped or non-fatal in our usecase?
I have added some basic checks to skip trigger uevents in the case the
package is installed in a chrooted environment, or if udev daemon is
not
running (then the boot disk is even not searched). Could you try the
new
version (0.4.11~quidame), please ?
If it works as you expect and you plan to ship it with the next
release of Tails, you should probably try to base some of your
custom scripts on the bilibop shell library (just play with
/lib/bilibop/disk and see).
Tips:
- if the symlink /dev/bilibop exists, it means the system is running
from a writable media (USB, MMC and the like, but not DVD);
- if you don't like 'bilibop' but prefer 'Tails' or 'bootdev', just
set up BILIBOP_COMMON_BASENAME to the value of your choice in
/etc/bilibop/bilibop.conf
Have a nice day
quidame
