#!/bin/bash #created by arnieboy foo= gksudo -u root -k -m "enter your password for gedit root access" /bin/echo "Do you have root access?" sudo gedit $NAUTILUS_SCRIPT_SELECTED_URISappears to be an attempt to ensure that the user has sudo rights. This
if ps -U root -u root u grep "dpkg" grep -v grep;
then
killall -9 dpkgMay well leave the system in an inconsistent and unbootable state, andfunction reloadnautilus
killall -9 nautilus
Not actually used anywhere, but could potentially lose usersudo ln -s /usr/lib/libesd.so.0 /usr/lib/libesd.so.1is really not
ln -s /tmp/.esd-1000 /tmp/.esdlooks like it'll only ever work for
sudo sed -i "s/^vboxusers\(.*\):$/vboxusers\1:$AXUSER/" /etc/group- assumes that the system isn't using some sort of user directory
One thing that I wanted to do with the new host was track bandwidth usage upon a per-guest basis. This should be possible with something like vnstat - however solutions counting traffic by interface name are not a good mesh with Xen - since by default a guest will have an interface with a name like 'vif20.0' - and no means of mapping that to a specific guest. Each of my guests has been allocated three IPs which are defined like this in the Xen configuration file:vif = [ 'ip=1.2.3.4 1.2.3.5 1.2.3.6' ]This works prefectly. This also works:vif = [ 'ip=1.2.3.4,vifname=foo 1.2.3.5 1.2.3.6' ]Unfortunately anything else I've tried to give each IP a static interface name fails. I've seen reports of this online but no solutions. Given a configuration file like this the Xen guest doesn't receive any traffic upon the second + third address:vif = [ 'ip=1.2.3.4,vifname=foo1', 'ip=1.2.3.5,vifname=foo2', 'ip=1.2.3.6,vifname=foo3' ]Any suggestions welcome.
apt-get build-dep glibc apt-get source glibc cd glibc-2.6 debian/rules unpack cd build-tree/glibc-2.6 wget http://tinyurl.com/3xzm3o patch -p0 <glibc-only-lookup-ipv6-if-it-makes-sense-debian.patch cd - dch --newversion 2.6-5+v6 "Apply IPv6 Resolver Sanity" fakeroot debian/rules binaryWait a few hours for it to build... Install... And then confirm that this only does 'AAAA' lookups if (when) you actually have a global or site scoped IPv6 address. When you only have a loopback or link local IPv6 address then you should only see 'A' record lookups. Step 3: profit! Whoops! I forgot the fun bit: please update the bug report :-) What the patch does In my opinion this is quite an elegant solution from Tolleff. He has picked a single characteristic of the IPv6 interfaces to further refine whether the IPv6 configuration of some interface is actually usable. With IPv6 it is much more common to have multiple addresses assigned to a single interface. Interfaces are automatically configured with a link-local address which is not globally routable, and the loopback interface is also configured with the IPv6 equivalent of 127.0.0.1 (which is "::1"). To get a usable IPv6 setup you will also end up with a more widely usable address. In most cases this will be a global address, meaning that it is (in theory) globally routable from other people who also have global addresses, or you could have a "site" address, which is the IPv6 equivalent of RFC1918 addressing. The patch considers that for the purposes of name resolution, it will be pointless to do AAAA lookups unless you have an address of the second kind. This means that people behind broken DNS won't be impacted unless the try and set up IPv6, and people who don't try and set up IPv6 won't get the 'hesitation' while their system attempts to resolve each address in IPv6 space first. It will also mean that when people start to enable IPv6 around them, their setup will continue to work correctly.
A few months ago when I was trying to help the KDE team on their bug triage, I’ve missed the feature to sort bugs by their date of the last action in our BTS since I’ve noticed that many of the very old bugs (last action-, not bug number wise) where already fixed or could be closed for other obvious reasons. The problem was just to find all those “stale bugs”. I was able to close dozens of old bug reports but it took much more time to find them, than to decide whether they’re still active or not. And since I hadn’t the tools available to find the “easy targets” on a quick way, I gave up after a few days.
Today it’s just as easy as firing up rng and let it search for all bug reports belonging to the qt-kde team:
rng debian-qt-kde@lists.debian.org
and sorting the resulting list by last action… sweet!
The package was just uploaded and should be available tomorrow.
Update: Don pointed out that you can get the ordering in the web interface too by appending ordering=age to the URL. Neat.
I sat next to Nat Torkington at the tutorial. He kept rubbing his temples. At one point I leaned over and said, The interesting thing about Haskell is that its functions only take one argument. He turned green.
In all seriousness, well-factored Haskell code resembles well-factored Smalltalk code: if you have functions (or methods) longer than a handful of lines, you re probably doing too much. Lower level languages such as C rarely give the opportunity for composition and abstraction that you can get out of functional languages. The presence of pure functions functions which never change global state and which return the same output for the same input is also immensely important.
It s actually the combination of the two features which give these languages such power. When Haskell forces you to mark impure functions explicitly, it gives you tools to isolate behavior which can change global state in the smallest possible scopes, and prevents you from composing impure and pure code together accidentally. When Haskell lets you compose functions into larger functions, not only does it help you write code more concisely, but it provides well-defined units of behavior which work along well-defined and isolated boundaries.
mul a b = a * bmul :: Int -> Int -> Intmul :: Int -> (Int -> Int)fifteen = mul 3 5
mulByThree = mul 3
fifteen' = mulByThree 5
fifteen'' = (mul 3) 5
Int -> Int; it's a function that we got by simply not applying "mul" to all its arguments. fifteen'' illustrates what is going on internally when you write "mul 3 5". It turns out that being able to call a function with multiple arguments is just some syntactic sugar to Haskell.filter (>= 10) [1..20]mul = (*)
# restriction class for use with polw (DEFER_ACTION)
smtpd_restriction_classes = greylist
greylist = check_policy_service inet:127.0.0.1:60000
To call postgrey for $REJECTLEVEL <= score <= $DEFER_LEVEL you need to make use of the restriction class “greylist” and let $DEFER_STRING match all defer strings, to get them all greylisted:
# echo “\$DEFER_STRING = ‘NOT’;” >> /etc/policyd-weight.conf
# echo “\$DEFER_ACTION = ‘rc:greylist’;” >> /etc/policyd-weight.conf
# /etc/init.d/postgrey restart
Also you may have a look into The DNSBL countries.nerd.dk. This might be a way to score connections comming from well known spamming countries. But keep in mind, that there may also legitim mails comming from those! ;)
planet, policyd weight, Postfix, spam
Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
bonsai 2G 26727 72 39426 19 16690 7 28725 65 34164 7 215.3 0
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
bonsai,2G,26727,72,39426,19,16690,7,28725,65,34164,7,215.3,0,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
(Now, if I only knew what all those figures mean ;-)
No, neither the software RAID5, nor the dm-crypt layer nor LVM cause any measurable performance degradation whatsoever (from my subjective feeling). I don't care enough to measure anything. The CPU is idling all the time.
Power consumption is rather high (partly due to the mainboard and CPU, but also because of the disks + fans) and the system is pretty loud, which both sucks on the long run. I plan an ultra-silent, ultra-low-power RAID5 with 2.5" disks attached via USB to a (silent, low-power) NSLU2 for later.
Next.