- Arch-general - lists.archlinux.org

Re: [arch-general] [arch-dev-public] BIND10? No, thanks.
by Genes Lists 10 Mar '13

10 Mar '13

On 03/08/2013 09:27 PM, Gaetan Bisson wrote: > Hi guys, > > Currently we use the BIND code base in two packages: > - dnsutils from [core] provides basic DNS query tools; > - bind from [extra] is the actual name server. ... > > We already have ldns in [core], a much better written (and sane) DNS > library which includes query tools that are near drop-in replacements > for BIND's: use `drill` instead of `dig`, etc. > Hi One observation - bind is the de facto standard and as far as I can tell used by the majority of the root servers [1] (and the majority of all major DNS servers according to wikipedia [2] and bind website [3] anyway :-)). We may want to be cautious stepping away from the dominant DNS software unless there is a sea change for the DNS community to do same. A casual look around [4] - so clearly I am not in the know here - but the rewrite seems not dissimilar to the postfix "re-write" of sendmail - modularity and security seemingly key goals. [5] Anyway, I'd encourage that we try and stick with bind. gene [1] http://en.wikipedia.org/wiki/Root_name_server [2] http://en.wikipedia.org/wiki/BIND [3] https://www.isc.org/wordpress/software/bind10/ [4] http://bind10.isc.org/wiki/DesignOverview [5] I am not familliar with ldns or it's benefits - security or other so I don't feel entitled to an opinion.

3 3

[arch-general] nouveau or kernel which one ?
by P .NIKOLIC 09 Mar '13

09 Mar '13

Hi for the last 3 kernels i have been getting errors and hangs that ultimately end in a completely frozen system this is the error that appears in the in the log Mar 07 11:00:43 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 4 Get 0xfffffffffc Put 0x0000fffff8 IbGet 0x000001fe IbPut 0x000001ff State 0xc0040022 (err: MEM_FAULT) Push 0x00400040 Mar 07 11:45:27 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002893c Put 0x0020029774 IbGet 0x0000035a IbPut 0x0000035b State 0x80004861 (err: INVALID_CMD) Push 0x00400040 Mar 07 11:54:36 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 4 Get 0xfffffffffc Put 0x0000fffff8 IbGet 0x00000237 IbPut 0x00000238 State 0xc0040022 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:00:14 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002bd20 Put 0x002002bd80 IbGet 0x000002ff IbPut 0x00000300 State 0xc0000020 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:16:33 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002d538 Put 0x002002d554 IbGet 0x00000243 IbPut 0x00000244 State 0x80000314 (err: INVALID_CMD) Push 0x00400040 Mar 07 12:21:09 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020035140 Put 0x002003af14 IbGet 0x00000362 IbPut 0x00000365 State 0x80004861 (err: INVALID_CMD) Push 0x00400040 Mar 07 12:25:06 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020030ad4 Put 0x0020030b8c IbGet 0x000001bc IbPut 0x000001bf State 0xc0000020 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:25:42 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020037348 Put 0x0020037e78 IbGet 0x0000035a IbPut 0x0000035b State 0xc0004861 (err: MEM_FAULT) Push 0x00400040 Mar 07 13:02:36 7-of-9 kernel: delay: estimated 192, actual 0 Mar 07 13:04:22 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 4 Get 0x00200d4984 Put 0x00200d4d1c IbGet 0x00000250 IbPut 0x00000251 State 0x8000745c (err: INVALID_CMD) Push 0x00400040 Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_BITFIELD Mar 07 13:04:22 7-of-9 kernel: nouveau [ PGRAPH][0000:01:00.0] DATA_ERROR Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 4 [0x003f96e000] subc 3 class 0x8597 mthd 0x1458 data 0xffffffff Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PFB][0000:01:00.0] trapped read at 0x0000000000 on channel 0x0003f96e PFIFO/PFIFO_READ/PUSHBUF reason: PT_NOT_PRESENT Mar 07 13:11:59 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020008fe4 Put 0x0020008ff8 IbGet 0x00000327 IbPut 0x00000329 State 0x80000064 (err: INVALID_CMD) Push 0x00400040 Mar 07 13:11:59 7-of-9 kernel: nouveau [ PFIFO][0000:01:00.0] CACHE_ERROR - Ch 2/0 Mthd 0x0060 Data 0xffffffff at present running KDE 4.10.1 kernel 3.7.10-1 4Gb ram currently running with 2.56Gib free memory video card is a GeForce GT220 @1Gb memory. Twin monitors USB external sound card (onboard card is pants) New install middle of January Thanks Pete . -- Linux 7-of-9 3.7.10-1-ARCH #1 SMP PREEMPT Thu Feb 28 09:50:17 CET 2013 x86_64 GNU/Linux

2 2

Re: [arch-general] [arch-dev-public] FYI: systemd 198
by Leonid Isaev 09 Mar '13

09 Mar '13

On Fri, 8 Mar 2013 09:35:39 +0900 Tom Gundersen <teg(a)jklm.no> wrote: > Hi guys, > > A new systemd release is out (not yet packaged though), and there are > several features which might be of interest to us. > > Cheers, > > Tom > > ---------- Forwarded message ---------- > From: Lennart Poettering <lennart(a)poettering.net> > Date: Fri, Mar 8, 2013 at 8:12 AM > Subject: [systemd-devel] [ANNOUNCE] systemd 198 > To: systemd Mailing List <systemd-devel(a)lists.freedesktop.org> > > > Hey! > > Finally, here's 198, with many big changes: > > http://www.freedesktop.org/software/systemd/systemd-198.tar.xz > > In detail: > > * Configuration of unit files may now be extended via drop-in > files without having to edit/override the unit files > themselves. More specifically, if the administrator wants to > change one value for a service file foobar.service he can > now do so by dropping in a configuration snippet into > /etc/systemd/systemd/foobar.service.d/*.conf. The unit logic > will load all these snippets and apply them on top of the > main unit configuration file, possibly extending or > overriding its settings. Using these drop-in snippets is > generally nicer than the two earlier options for changing > unit files locally: copying the files from > /usr/lib/systemd/system/ to /etc/systemd/system/ and editing > them there; or creating a new file in /etc/systemd/system/ > that incorporates the original one via ".include". Drop-in > snippets into these .d/ directories can be placed in any > directory systemd looks for units in, and the usual > overriding semantics between /usr/lib, /etc and /run apply > for them too. > > * Most unit file settings which take lists of items can now be > reset by assigning the empty string to them. For example, > normally, settings such as Environment=FOO=BAR append a new > environment variable assignment to the environment block, > each time they are used. By assigning Environment= the empty > string the environment block can be reset to empty. This is > particularly useful with the .d/*.conf drop-in snippets > mentioned above, since this adds the ability to reset list > settings from vendor unit files via these drop-ins. > > * systemctl gained a new "list-dependencies" command for > listing the dependencies of a unit recursively. > > * Inhibitors are now honored and listed by "systemctl > suspend", "systemctl poweroff" (and similar) too, not only > GNOME. These commands will also list active sessions by > other users. > > * Resource limits (as exposed by the various control group > controllers) can now be controlled dynamically at runtime > for all units. More specifically, you can now use a command > like "systemctl set-cgroup-attr foobar.service cpu.shares > 2000" to alter the CPU shares a specific service gets. These > settings are stored persistently on disk, and thus allow the > administrator to easily adjust the resource usage of > services with a few simple commands. This dynamic resource > management logic is also available to other programs via the > bus. Almost any kernel cgroup attribute and controller is > supported. > > * systemd-vconsole-setup will now copy all font settings to > all allocated VTs, where it previously applied them only to > the foreground VT. > > * libsystemd-login gained the new sd_session_get_tty() API > call. > > * This release drops support for a few legacy or > distribution-specific LSB facility names when parsing init > scripts: $x-display-manager, $mail-transfer-agent, > $mail-transport-agent, $mail-transfer-agent, $smtp, > $null. Also, the mail-transfer-agent.target unit backing > this has been removed. Distributions which want to retain > compatibility with this should carry the burden for > supporting this themselves and patch support for these back > in, if they really need to. Also, the facilities $syslog and > $local_fs are now ignored, since systemd does not support > early-boot LSB init scripts anymore, and these facilities > are implied anyway for normal services. syslog.target has > also been removed. > > * There are new bus calls on PID1's Manager object for > cancelling jobs, and removing snapshot units. Previously, > both calls were only available on the Job and Snapshot > objects themselves. > > * systemd-journal-gatewayd gained SSL support. > > * The various "environment" files, such as /etc/locale.conf > now support continuation lines with a backslash ("\") as > last character in the line, similar in style (but different) > to how this is supported in shells. > > * For normal user processes the _SYSTEMD_USER_UNIT= field is > now implicitly appended to every log entry logged. systemctl > has been updated to filter by this field when operating on a > user systemd instance. > > * nspawn will now implicitly add the CAP_AUDIT_WRITE and > CAP_AUDIT_CONTROL capabilities to the capabilities set for > the container. This makes it easier to boot unmodified > Fedora systems in a container, which however still requires > audit=0 to be passed on the kernel command line. Auditing in > kernel and userspace is unfortunately still too broken in > context of containers, hence we recommend compiling it out > of the kernel or using audit=0. Hopefully this will be fixed > one day for good in the kernel. > > * nspawn gained the new --bind= and --bind-ro= parameters to > bind mount specific directories from the host into the > container. > > * nspawn will now mount its own devpts file system instance > into the container, in order not to leak pty devices from > the host into the container. > > * systemd will now read the firmware boot time performance > information from the EFI variables, if the used boot loader > supports this, and takes it into account for boot performance > analysis via "systemd-analyze". This is currently supported > only in conjunction with Gummiboot, but could be supported > by other boot loaders too. For details see: > > http://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface > > * A new generator has been added that automatically mounts the > EFI System Partition (ESP) to /boot, if that directory > exists, is empty, and no other file system has been > configured to be mounted there. > > * logind will now send out PrepareForSleep(false) out > unconditionally, after coming back from suspend. This may be > used by applications as asynchronous notification for > system resume events. > > * "systemctl unlock-sessions" has been added, that allows > unlocking the screens of all user sessions at once, similar > how "systemctl lock-sessions" already locked all users > sessions. This is backed by a new D-Bus call UnlockSessions(). > > * "loginctl seat-status" will now show the master device of a > seat. (i.e. the device of a seat that needs to be around for > the seat to be considered available, usually the graphics > card). > > * tmpfiles gained a new "X" line type, that allows > configuration of files and directories (with wildcards) that > shall be excluded from automatic cleanup ("aging"). > > * udev default rules set the device node permissions now only > at "add" events, and do not change them any longer with a > later "change" event. > > * The log messages for lid events and power/sleep keypresses > now carry a message ID. > > * We now have a substantially larger unit test suite, but this > continues to be work in progress. > > * udevadm hwdb gained a new --root= parameter to change the > root directory to operate relative to. > > * logind will now issue a background sync() request to the kernel > early at shutdown, so that dirty buffers are flushed to disk early > instead of at the last moment, in order to optimize shutdown > times a little. > > * A new bootctl tool has been added that is an interface for > certain boot loader operations. This is currently a preview > and is likely to be extended into a small mechanism daemon > like timedated, localed, hostnamed, and can be used by > graphical UIs to enumerate available boot options, and > request boot into firmware operations. > > * systemd-bootchart has been relicensed to LGPLv2.1+ to match > the rest of the package. It also has been updated to work > correctly in initrds. > > * Policykit previously has been runtime optional, and is now > also compile time optional via a configure switch. > > * systemd-analyze has been reimplemented in C. Also "systemctl > dot" has moved into systemd-analyze. > > * "systemctl status" with no further parameters will now print > the status of all active or failed units. > > * Operations such as "systemctl start" can now be executed > with a new mode "--irreversible" which may be used to queue > operations that cannot accidentally be reversed by a later > job queuing. This is by default used to make shutdown > requests more robust. > > * The Python API of systemd now gained a new module for > reading journal files. > > * A new tool kernel-install has been added that can install > kernel images according to the Boot Loader Specification: > > http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec > > * Boot time console output has been improved to provide > animated boot time output for hanging jobs. > > * A new tool systemd-activate has been added which can be used > to test socket activation with, directly from the command > line. This should make it much easier to test and debug > socket activation in daemons. > > * journalctl gained a new "--reverse" (or -r) option to show > journal output in reverse order (i.e. newest line first). > > * journalctl gained a new "--pager-end" (or -e) option to jump > to immediately jump to the end of the journal in the > pager. This is only supported in conjunction with "less". > > * journalctl gained a new "--user-unit=" option, that works > similar to "--unit=" but filters for user units rather than > system units. > > * A number of unit files to ease adoption of systemd in > initrds has been added. This moves some minimal logic from > the various initrd implementations into systemd proper. > > * The journal files are now owned by a new group > "systemd-journal", which exists specifically to allow access > to the journal, and nothing else. Previously, we used the > "adm" group for that, which however possibly covers more > than just journal/log file access. This new group is now > already used by systemd-journal-gatewayd to ensure this > daemon gets access to the journal files and as little else > as possible. Note that "make install" will also set FS ACLs > up for /var/log/journal to give "adm" and "wheel" read > access to it, in addition to "systemd-journal" which owns > the journal files. We recommend that packaging scripts also > add read access to "adm" + "wheel" to /var/log/journal, and > all existing/future journal files. To normal users and > administrators little changes, however packagers need to > ensure to create the "systemd-journal" system group at > package installation time. > > * The systemd-journal-gatewayd now runs as unprivileged user > systemd-journal-gateway:systemd-journal-gateway. Packaging > scripts need to create these system user/group at > installation time. > > * timedated now exposes a new boolean property CanNTP that > indicates whether a local NTP service is available or not. > > * systemd-detect-virt will now also detect xen PVs > > * The pstore file system is now mounted by default, if it is > available. > > * In addition to the SELinux and IMA policies we will now also > load SMACK policies at early boot. > > Contributions from: Adel Gadllah, Aleksander Morgado, Auke > Kok, Ayan George, Bastien Nocera, Colin Walters, Daniel Buch, > Daniel Wallace, Dave Reisner, David Herrmann, David Strauss, > Eelco Dolstra, Enrico Scholz, Frederic Crozat, Harald Hoyer, > Jan Janssen, Jonathan Callen, Kay Sievers, Lennart Poettering, > Lukas Nykryn, Mantas Mikulėnas, Marc-Antoine Perennou, Martin > Pitt, Mauro Dreissig, Max F. Albrecht, Michael Biebl, Michael > Olbrich, Michal Schmidt, Michal Sekletar, Michal Vyskocil, > Michał Bartoszkiewicz, Mirco Tischler, Nathaniel Chen, Nestor > Ovroy, Oleksii Shevchuk, Paul W. Frields, Piotr Drąg, Rob > Clark, Ryan Lortie, Simon McVittie, Simon Peeters, Steven > Hiscocks, Thomas Hindoe Paaboel Andersen, Tollef Fog Heen, Tom > Gundersen, Umut Tezduyar, William Giokas, Zbigniew > Jędrzejewski-Szmek, Zeeshan Ali (Khattak) > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > _______________________________________________ > systemd-devel mailing list > systemd-devel(a)lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel With this release, I have a minor issue with shutdown/reboot as a normal user from tty, if the _same_ tty saw a root login and subsequent logout earlier. I _guess_, this is also true for any other user, not only root. So: 1. Power on -> login as a user to tty -> systemctl poweroff works OK. 2. Power on -> login as root to tty; do something; logout -> login as user to same tty -> systemctl poweroff yields :User root is logged in on tty1. :Please retry operation after closing inhibitors and logging out other :users. Alternatively, ignore inhibitors and users with 'systemctl poweroff :-i'. Meanwhile, systemd-inhibit --list says there are 0 inhibitors, ps shows no root shells, and loginctl shows no leftover root sessions. I have all default configs... So what am I missing here? Thanks in advance, -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D

1 0

[arch-general] makechrootpkg vs. namcap
by Lieven Moors 09 Mar '13

09 Mar '13

Hi, I was building a package using makechrootpkg, and the build was failing because a mandatory dependency was missing. But when I add the dependency, namcap complains that it is not needed. I was wondering how namcap checks dependencies, and what the particular shortcommings are of namcap when detecting dependencies. I was also wondering if there could be a possibility that namcap is right, and that something else goes wrong while doing the chroot-build. I would be grateful if somebody could enlighten me a little in this... Greetings, lieven

2 3

Re: [arch-general] Virtualbox guest additions on custom kernel
by Ralf Mardorf 09 Mar '13

09 Mar '13

I suspect you're missing an optional dependency. $ pacman -Si virtualbox-guest-utils | grep non-stock Optional Deps : virtualbox-guest-dkms: Guest kernel source modules for non-stock kernels It's likely that it will work as it does work for the host, https://wiki.archlinux.org/index.php/VirtualBox#Hosts_running_a_custom_kern… , IOW I guess you need to install "virtualbox-guest-dkms", then run # dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k $(uname -rm|sed 's/\ /\//') and after that to load the modules.

1 0

[arch-general] Virtualbox guest additions on custom kernel
by Pietro Paolini 09 Mar '13

09 Mar '13

Hello all, I compiled my own custom kernel on a virtual machine and then I need to provide at my system the additions in order to have a compelete system. I tried to follow the https://wiki.archlinux.org/index.php/VirtualBox#Install_the_Guest_Additions but I catch an error on # modprobe -a vboxguest vboxsf vboxvideo FATAL: module vboxdrv not found And under /lib/modules/mykernel/ or /lib/modules/extra-mykernel I can't find the modules, do I compile by hands the module, any suggestions ? Hope this is the right place where ask, thanks in advance, Pietro

1 0

[arch-general] UEFI madness
by David Benfell 08 Mar '13

08 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, So far, my attempt to install Arch Linux on a UEFI system is a total facepalm moment. The problem is in booting post-install. So, first, does anyone have actual--and successful--experience installing Arch on a UEFI system? Yes, I went to the Arch Wiki, which initially pointed me at GummiBoot. There are actually two sets of instructions, one given where I looked first, for the UEFI entry, and another under the entry for GummiBoot. Neither succeeds, but I wound up following the latter set of instructions (and cleaning up extra entries with efibootmgr, which fortunately makes this relatively easy). GummiBoot says it can't find /vmlinuz-linux. I tried modifying the configuration to say /boot/vmlinuz-linux, but no joy. Apparently, I'm really supposed to copy this file and the initrd image to the EFI partition, but nobody says where in the EFI partition, so I have no idea. I also tried following the instructions for grub-efi. I'm just mystified. I managed to install the right package, but from there I just wasn't understanding a thing. I've been using linux since 1999 so this shouldn't be so completely mystifying. I tried installing rEFInd (from sourceforge). As near as I can tell, it does indeed detect all the possible boot options on the system. But when I try booting the Arch installation, it says it can't find the root partition. It also detects the GummiBoot option, but that leads the same place as before. Finally, it detects the Windows option, which I hope still works (unfortunately I do need this). I guess getting something that just works--like it did with BIOS systems--is not in the cards. What do I do now? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRMZ+5AAoJELJhbl/uPb4SAA4P/3xG4C5viqdgdZhtZ72hFC9v VLBWw9CguzTvqYMydO4TTqwpyObW0iPFMWRzlkMt7YjmC83qgQJDAI1P7KR4fpHE fHjyqS7IKFnLe4ckKnKJIQMGeEbwcsAaF0Loy/22dW+5U10IRy39NIlvUdWQJKtc O7vpch/lZ2DKFd7zmKgKLu2FLuZK0FvwN2cGH91cYP66rloqaXytXWLZ3IIvCtf5 mGJqwx4CjKWf3FefFANXYsPtb4rmfbE1xl/xeIT4OH0F+0H77EFhFTkBsDknYnHM pUg9B5pHmJ+xMiVSDIYYIXpgT/Spk9DWp4+PZN5N8GBE63J8kzWuUqTVV/XVyR1x 0aZCJAo0Ke+swBa6cGZ/WSWRqA4kP9nJBtJ00qX+PE3FFFd8vjYyP7Qz0cmIhfqV VHx3UXzI9Q8EkMzlENWD79M+WHLeUPQopsdfmWOOI1E7N+5seeFRmekmB+jY1NRJ uXNPCq5w0iIaWB4KuAmchbP3qtoGxU5oXJ5IPh3NQOIdbScN0+4l6HtOmnxMQ2H1 HyR/2nV0e5rvuhsuKBn2ZGyLOvYN6I9AjFBPI5VmY2Ansy750AOOBqXIPLlBouqb Oy0h26dfyn8RdlcoYm4QlXzra1p6ZBk5dJ9GxYhVsXxAaUnlrprXtk3HPQcIjpiS I4n74T8MiK5TxjSDJO60 =6UgK -----END PGP SIGNATURE-----

9 19

Re: [arch-general] [wpa_actiond 1.4] slow disconnects
by Thomas Bächler 08 Mar '13

08 Mar '13

Am 05.03.2013 16:44, schrieb Pali Rohár: > Hello, > > On Tuesday 05 March 2013 10:23:24 Thomas Bächler wrote: >> Am 04.03.2013 21:26, schrieb Leonid Isaev: >>> Hi, >>> >>> With testing/wpa_actiond-1.4 I am having a minor problem >>> when shutting down net-auto-wireless.service: 'systemctl >>> stop net-auto-wireless.service' pauses for ~10sec before >>> finally disconnecting. Of course, this also occurs on >>> normal system poweroff (which is usually ~5sec). The wifi >>> network is WPA "enterprise" (important entries in >>> wpa_supplicant.conf: key_mgmt=WPA-EAP; eap=PEAP; >>> phase1="peaplabel=0"; phase2="auth=MSCHAPV2"), and piece of >> >>> daemon.log after the above delay has elapsed: >> I've seen this too, but I didn't determine yet that is was >> wpa_actiond's fault. There are several issues here: >> >> 1) I am unsure what exactly terminates wpa_actiond. > > Before my patches wpa_actiond could be terminated only by > KILL/TERM signals or correct "terminate" event from > wpa_supplicant. wpa_supplicant sending terminate event only if > wpa_supplcant is stopped regulary (when wpa_supplicant is killed > by KILL no terminate event is sent!). With my patches wpa_actiond > is also terminated when wpa_supplicant is KILLed. > >> 2) net-auto-wireless.service is Type=forking, but has no >> proper MainPID detected, so systemd doesn't know what exactly >> to kill. >> >> This change however seems to be related to Pali's changed, so >> I'm CC'ing him to see if he knows what this might be about. > > You can always stop wpa_actiond with KILL or TERM signals. I did > not removed any code which handling stopping wpa_actiond. I only > added another check if wpa_actiond should exit. > > So my patches should not change behaviour of stopping > wpa_actiond. Problem is maybe in blackbox which starting and > stoppping wpa_actiond. I'm not using that systemd and this is > another reason against it. Not easy to understand and debug this > problem. > > I tested my patches on my system without systemd and wpa_actiond > working without problem. Really I cannot help you with blackbox > which I not using... This may even be related to the way netcfg stops wpa_actiond (it doesn't - it only stops wpa_supplicant). One can probably debug this easily by making wpa_actiond more verbose.

2 1

[arch-general] virtualbox-host-dkms
by Ralf Mardorf 08 Mar '13

08 Mar '13

Hi :) dkms can't rebuild deleted vbox modules for the "linux" kernel # dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k $(uname -rm|sed 's/\ /\//') Module vboxhost/4.2.8 already installed on kernel 3.7.10-1-ARCH/x86_64 # ls /usr/lib/modules/extramodules-3.7-ARCH/ version and for linux-rt I get the same error # dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k 3.6.11-rt30-1-rt/x86_64 Module vboxhost/4.2.8 already installed on kernel 3.6.11-rt30-1-rt/x86_64 but there never were modules installed for the kernel-rt. Regards, Ralf

3 4

[arch-general] Weird issue with Google Talk/Hangout plugin
by David Rosenstrauch 08 Mar '13

08 Mar '13

I'm having a weird issue with the Google Talk plugin (https://aur.archlinux.org/packages/google-talkplugin/) distorting all my video images - both the ones of me coming in from my camera, and the ones coming in from others across the Net. See http://www.darose.net/GoogleHangWeirdness.png for an example. Anyone have any idea what's going on here and/or how to fix? This seems to be a recent issue - i.e., probably caused by some package upgrade within the past week or so. I'm running google-talkplugin 3.14.17.0-1 with firefox 19.0-1. But I don't think the issue is caused by the plugin itself. (Or by firefox, since I see the same problem when I use Google chromium browser.) I was running an older version of the plugin - which had been working fine for weeks - when I started experiencing the issue. I upgraded to the latest version in an attempt to work around the problem, but it didn't clear it up. So as I said, I don't think the plugin itself is the cause of the problem - since 2 different versions of the plugin are experiencing the issue, and the issue popped up out of the blue after things had been working fine for quite a while. Any assistance anyone might be able to lend here would be much appreciated! Thanks, DR

1 1