Ugh. Ran apt-get upgrade. That was apparently a mistake, now morituri is broken... ImportError: When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject". See: https://bugzilla.gnome.org/show_bug.cgi?id=709183 .... well, that's nice, excpet doing that just leads to different errors.
And changing the capitalization gobject → GObject a few places leads to a gstreamer error, complaing about the lack of an Init call.
And calling that... just leads to moritori failing without an error message.
I've been getting a bit frustrated about the policykit thing, so I wrote to the mailing list - yes, there is one. However, it seems remarkably inactive. Does anyone actually use policykit, I wonder. Maybe it was created by an underground Satanic cult, who have now done their part by creating it, and can sit back to enjoy the frustration and despair.
@Gilles no, the underground Satanic cult is definitely the GNOME3 folks.
@Gilles the systemd folks are very above-ground with their Satanism.
The systemd folks brought you services that can't accidentally ignore stop, can restart on failure, don't have races with pid files, and can be easily run with security features like an isolated /tmp; their evil world domination plans are out in the open (just look at all the manpages...). GNOME folks, OTOH, ported the Registry to Linux.
(though we know their evil is underground because they disguised their registry in the form of text files)
@derobert the systemd brought us services that restart when you stop them, log files that aren't in text format, and partitioned the world into “requires systemd” and “incompatible with systemd”. GNOME's deficiencies, OTOH, can mostly be worked around.
@Gilles I think the 'requires systemd' software of note consists of only one thing... GNOME 3.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff77a5e68 in rc_conf_int () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
(gdb) bt
#0 0x00007ffff77a5e68 in rc_conf_int () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#1 0x00007ffff77a6038 in test_config () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#2 0x00007ffff77a6535 in rc_read_config () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#3 0x00005555555565c0 in ?? ()
#4 0x00007ffff6ff4b45 in __libc_start_main (main=0x555555556510, argc=11, argv=0x7fffffffeb18, init=<optimized …
... oh fun, no debug symbol package. Get to built it myself, I guess...
@FaheemMitha Upgrading the monitoring box, one of the probes it runs is it checks our RAIDUS servers, using a plugin that comes with Nagios (or at least Debian ships with it) called check_radius
@FaheemMitha Not particularly. But I get paid for it, so...
I would guess that whole mess was kluged together by some sysadmin who just needed the #(@!# to work, and didn't really know how to program. At least I'd hope that's t he explanation—if that was produced by a professional programmer, he/she should be ashamed.
Hey, does anyone know why some printers drivers e.g. Brother are proprietary. It's a bit weird, if you think about it. Do they think people can use it to reverse-engineer valuable engineering secrets?
> Unprivileged user can not mount NTFS block devices using the external FUSE library. Either mount the volume as root, or rebuild NTFS-3G with integrated FUSE support and make it setuid root.
> Mount is denied because setuid and setgid root ntfs-3g is insecure with the external FUSE library. Either remove the setuid/setgid bit from the binary or rebuild NTFS-3G with integrated FUSE support and make it setuid root.
Tags: patch
Removing "--with-fuse=external" or replacing it with
"--with-fuse=internal" in the configuration part of the rules files
solves the problem.
But apparently the maintainer is not buying this.
tag 631504 - patch
thanks
On 08/05/2011 09:21 AM, Christophe Monniez wrote:
> Is there a reason to use the external fuse library instead of the
> ntfs-3g internal one ?
security reasons and no code-duplication. the remaining issues with
using the systems fuse should be fixed in the code, the internal one is
not an acceptable workaround.
Sometimes maintainers are just wacky. Code duplication? Really?
Ok, now I'm confused. The version in jessie is using the internal library.
@Braiam That's a machine-generated configure file. It was not meant to be viewed by mortal eyes. Be careful, your eyeballs will shrivel up and fall out of their sockets.
~$ dmesg | tail
[ 479.558062] usb 1-1: SerialNumber: S07F1601A00000090095
[ 479.559231] scsi7 : usb-storage 1-1:1.0
[ 480.557093] scsi 7:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4
[ 480.558308] sd 7:0:0:0: Attached scsi generic sg1 type 0
[ 480.559916] sd 7:0:0:0: ...
