Adam in t-shirt is the only one appropriately dressed. Regards, a Finn

Karhua ja hyaarlgh

Karhuu ja… husaa?

You and your imperial currencies. We need an SI unit for money.

On 12.04 at least, the target is governed by cupsd’s AppArmor profile (see bug #147551) and trying to circumvent it using symlinks fails irrespective of whether the target is on another filesystem or not (”failed to set file mode for PDF file” in /var/log/cups/cups-pdf_log).

As per bug #147551, when the default target directory is changed in cups-pdf.conf, cups-pdf silently fails to print anything until a corresponding change is made in the usr.sbin.cupsd AppArmor profile. The ”Out” key in cups-pdf.conf is preceded by commented notes about the usage, but the AppArmor requisition goes unmentioned, apparently causing confusion among users. I suggest something like the attached patch be applied to cups-pdf.conf to document this.

From your title I thought this was going to be one of those ”sleeping dog whining and twitching because of nightmares” videos.

Just making a note about similarity between this and bug #939301; latter perhaps a duplicate?

umount.crypt doesn’t support lazy unmounting:

jani@saegusa:~$ sudo mount .Backup
Password:
jani@saegusa:~$ grep Backup /etc/mtab
/dev/sdc1 /home/jani/.Backup crypt rw,nosuid,nodev,noauto 0 0
jani@saegusa:~$ sudo umount -l .Backup
Unknown option: -l
Usage: umount.crypt [-fnrv] [-?|–help] [–usage]
Unknown option: -l
Usage: umount.crypt [-fnrv] [-?|–help] [–usage]

The usefulness of -l is documented in umount(8).

Strangely, the Debian BTS claims this feature has already been implemented ages ago [1].

*[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=370526

We perhaps could have avoided at least some of the public nonsense by calling the LHC a ”Detector” rather than a ”Collider”, as it’s actually just the detection of these events that’s somewhat outside of what nature does by itself all the time.