On Sat, 07 Apr 2012 00:48:09 +0200, Samuraiii wrote:
I'm trying to autodisable wifi when lan cable is plugged in.
I found rfkill ebuild which look like something I need but I'm
clueless where to get state of the ethernet card.
You could do this with ifplugd, but the easiest way is with Wicd,
My Dell XPS 13 Ultrabook goes to maximum brightness whenever I close
the top and I have to execute the following command in order to
control the brightness again:
echo 0 /sys/class/backlight/intel_backlight/brightness
The following script in /etc/pm/sleep.d/ is said to fix the problem:
On 5 April 2012 15:42, Neil Bothwick n...@digimed.co.uk wrote:
On Thu, 05 Apr 2012 17:59:42 +0200, Dan Johansson wrote:
I have a similar thing on my ~x86, but the difference is that I know
why I get it. I have successfully be able to create an initramfs
that does a vgscan, vgchange
On 6 April 2012, at 13:42, Volker Armin Hemmann wrote:
…
So my question still stands, does anyone know where there FFTOOLS
flags are documented?
some are - here :
http://wiki.multimedia.cx
and for others: there is always google…
LOL. Because you'd be having a laugh if you were
On Sat, 7 Apr 2012 02:47:41 -0600, Carlos Sura wrote:
The problem is that it is trying to write to /var/lock, which is on /
at this point, rather than /run/lock, which is on a writeable tmpfs.
I got this error, and saw a bugfile on Gentoo, just downgrade to your
previous working version
I am using a single BT usb dongle to communicate over rfcomm with two BT
Arduino based devices. Individually they work fine but if one is connected (to
rfcomm1), but any attempt to use the other (rfcomm0) fails and knocks the first
into limbo requiring recovery.
The BT spec implies up to 8
i realized my problems trying to rebuild digikam-2.5.0 were related to the
latest version of media-libs/libmp4v2 (1.9.1_p479), that i had upgraded a
couple of days ago.
after masking it and downgrading to libmp4v2-1.9.1, i could compile digikam
again. problems that i was having compiling other
On Sat, 7 Apr 2012 11:38:40 +0100
Neil Bothwick n...@digimed.co.uk wrote:
On Sat, 7 Apr 2012 02:47:41 -0600, Carlos Sura wrote:
The problem is that it is trying to write to /var/lock, which is
on / at this point, rather than /run/lock, which is on a
writeable tmpfs.
I got this
On Saturday 07 Apr 2012 16:28:39 Alan McKinnon wrote:
On Sat, 7 Apr 2012 11:38:40 +0100
Neil Bothwick n...@digimed.co.uk wrote:
On Sat, 7 Apr 2012 02:47:41 -0600, Carlos Sura wrote:
The problem is that it is trying to write to /var/lock, which is
on / at this point, rather than
I've come across this
http://johanlouwers.blogspot.com/2011/03/linux-check-interface-status.html
But this isn't helping me:
right now I'm on wifi only but when I run ifconfig I get this for
eth0 (my lan card)
eth0 Link
On Sat, 7 Apr 2012 17:28:39 +0200, Alan McKinnon wrote:
That bug report also showed the correct solution. There's no need to
downgrade, just change the locking_dir location from /var/lock
to /run/lock. Not only is this simpler and faster, it means another
update can't cause the same
11 matches
Mail list logo
