jinnantonnixx

You don't say! I sold my van recently, I was paying £500/year for tax and insurance, and only driving less than 2000 miles. Mrs Tonnixx has a car, and I just use my bicycle. If the tax was abolished completely, and the cost added to fuel I would have kept the van, but it just didn't make sense to own a vehicle that leaked money when not in use.

I'm guessing you've done this: How to be Authoritative for a Single Host Name in DNS | ITGeared.com Does it work for this problem - i.e. are your google searches using regular http (with the google bubble hinting at content filtering)?

I take it you're making a stub zone plus an 'A' record for http://www.google.com? We didn't want to do that. You can make an alias if you have a 2003 or 2008 server, but not 2008R2. Before 2008R2, it was possible to create a zone for http://www.google.com and add a single CNAME record which would successfully alias the name. The problem is fully covered here: http://social.technet.microsoft.com/Forums/en-US/eebd5c3f-8d96-4014-9852-f3028c71d930/implementing-cname-wwwgooglecom-pointing-to-nosslsearchgooglecom-without-making-dns-server?forum=winserverDS I'm very late to this party so the above kludge to the server's hosts will have do for now, unless there's a better solution.

The problem: Cannot filter queries as Google search is using SSL https://support.google.com/websearch/answer/186669?hl=en Google say: "To utilize the no SSL option for your network, configure the DNS entry for Google to be a CNAME for nosslsearch.google.com." Which is brilliant advice, but doesn't work on MS Server 2008R2 DNS. So, here's my kludge if it's of use to anyone. I'm using Squid on Centos servers, by the way. I wrote a bash script which runs daily and looks up the IP address for "nosslsearch.google.com" and adds these entries to the Squid server's hosts file. You must remove any 'dns_nameservers' from your squid.conf Here's the bash file which should live in /etc/cron.daily # rebuilds host file with google's non-ssl seach address # rename the existing hosts file mv /etc/hosts /etc/hosts.bak # copy the old hosts file to a new hosts file, minus any lines containing 'google' grep -v google /etc/hosts.bak > /etc/hosts # get the latest IP address IP_RESULT=`nslookup nosslsearch.google.com | tail -n 2 | cut -f 2 -d ":" | cut -f2 -d " "` #if IP_RESULT is not NXDOMAIN, add the new IP records, otherwise do nothing if [ "$IP_RESULT" != "NXDOMAIN" ] then echo $IP_RESULT www.google.co.uk >> /etc/hosts echo $IP_RESULT www.google.com >> /etc/hosts fi

All your Amazon packages would end up in the North Sea if they flew today.

I tried tyre liners, but had a pin-hole in the tube within two weeks. Out they came. I've been using Slime (tube additive) for a couple of weeks with success. I had a front puncture; it deflated a little but kept enough air to get to work. It had totally deflated, and took a total of three inflations to 'catch' the puncture, and it's held the pressure 100% since then without repair I had a minor 'pffft' on the rear tyre, lost a little air, but is holding. So Slime has already saved me (at least) two tube changes on a dark canal towpath.

A friend of mine is a competitive runner and he pointed me at this site. He swears by the method outlined here; most runners train above their ideal zone. Hopefully this is of some help. 180-Formula

This could be the decisive moment for Microsoft's fortunes: hit or bust.

Google Docs. Everything I need to remember goes in there. Copy and paste, name it something sensible and that's that. My work stuff is shared with colleagues, so they reap the fruitful bounties of my Googling. The search is second to none, so I can find a relevant document in no time. I don't even bother filing or organising notes, just stick it in the 'work stuff' folder and the search will pull out the relevant hits. Hasn't failed me yet. Hint: keep local copies of 'how to fix the internet'

Try adding these lines to a sample share (e.g. intake 5) then testing that particular logon. You'll need to restart samba of course. e.g. [intake05] path = /var/fshost/documents/intake05 write list=intake05 writeable = yes browseable = yes read only = no This might be of use http://www.samba.org/samba/docs/using_samba/ch09.html

In your smb.conf, under the relevent share(s) do you have writable=yes and write list = + ?

I've got an i3 (colour - hah!). What's this about Openmaps? Edit: Well check this out... http://www.mkgmap.org.uk/

Is the time on the server(s) accurate? Does wbinfo -t from the server show any erorrs? Does wbinfo -g show AD groups?

If there are any errors in those notes, please point out the corrections or clarifications needed. This is a good paper on LVM. The Linux Logical Volume Manager | Red Hat LVMs are extremely flexible and resizing a running machine's / volume is interesting stuff.

You add another PV consuming the new free space, then extend the volume group by adding the new PV. I've done exactly this quite recently. Almost incredibly, I took notes: Follow them to the letter and it works just fine (from experience) You might want to try a modern rescue image with a modern Gparted - it might be able to add the volume groups using the nice GUI. Note: these notes are written for my particular systems with two drives, but you'll get the principle. Extending a logical volume in a virtual machine running Red Hat or Cent OS (1006371) Purpose This article provides steps for extending the root partition residing in a logical volume created with Logical Volume Manager (LVM) in a virtual machine running Red Hat/Cent OS. Resolution To extend the logical volume: Note: These steps only apply to EXT3 file systems. Caution: VMware recommends having a complete backup of the virtual machine prior making these changes. Power off the virtual machine. Edit the virtual machine settings and extend the virtual disk size. For more information, see Increasing the size of a virtual disk (1004047). Probably don’t need this as the disks can be resized with the VMWare GUI. Boot with a GParted image and resize the partition. If you are using a version that will cope with LVM, you can skip the following few sections about resizing partitions. Power on the virtual machine. Identify the device name, which is by default /dev/sda, and confirm the new size by running the command: fdisk -l Create a new primary partition: Run the command: # fdisk /dev/sda (sdX depending the results of the step 4) If you get a message about invalid partition tables, use the ‘w’ command to write the changes. Reboot and continue. Press p to print the partition table to identify the number of partitions. By default there are 2: sda1 and sda2. Press n to create a new primary partition. Press p for primary. Press 3 for the partition number, depending the output of the partition table print. Press Enter two times. Press w to write the changes to the partition table. Restart the virtual machine. Run this command to verify that the changes were saved to the partition table and that the new partition has an 83 type: # fdisk -l Run this command to convert the new partition to a physical volume: # pvcreate /dev/sda3 Run this command to extend the physical volume: # vgextend VolGroup00 /dev/sda3 Note: To determine which volume group to extend, use the command vgdisplay. Run this command to verify how many physical extents are available to the Volume Group: # vgdisplay VolGroup00 | grep "Free" If you have used a modern GParted which can cope with LVM, you can drop in at this point as GParted will have already done the groundwork of extended the logical group. Run the following command to extend the Logical Volume: # lvextend -L+#G /dev/VolGroup00/LogVol00 Where # is the number of Free space in GB available as per the previous command. Note: to determine which logical volume to extend, use the command lvdisplay. Run the following command to expand the ext3 filesystem online, inside of the Logical Volume: # ext2online (or resize2fs) /dev/VolGroup00/LogVol00 Note: Use resize2fs instead of ext2online if it is not a Red Hat virtual machine. Run the following command to verify that the / filesystem has the new space available: # df -h /

Don't know yet, still on the POC stage. Very interesting. As is the beta they're testing - Owncloud Documents! Features | ownCloud.org It's still very basic, but promising stuff.

Google is covered by the 'Safe Harbor' which means that using it is acceptable under the UK's DPA. I don't know about iCloud. We're looking at a self-hosting cloud with Owncloud. The concerns you mention go away if you do this. ownCloud.org | Your Cloud, Your Data, Your Way! Install a Centos server then do this: software.opensuse.org: Install package isv:ownCloud:devel / owncloud-client

Let's not forget the baby cheeses. Babybells, DairyLees and so on.

This is, after all, the season of pizza goodwill towards all.

A surprise witness has been called. Enter 'Big Rigs'. The courtroom was in tears. Of laughter.

"ET" on the Atari 2600. The prosecution rests.

Have you thought about a home-brew? Something like a tiny HP Microserver (which I have), I think there are some good cash-back deals floating around. For an OS, if you don't fancy a stock OS (I use Centos), you can get a good-to-go NAS operating system for free, something like FreeNAS Project - Open Source Storage - FreeNAS Project Long term, this will be a far more flexible solution that any pre-packaged NAS systems.

Arise, old thread! Fickle old me. I've been quite a supporter of Unity for a while, but my Ubuntu 12.04 & a bunch of PPAs were getting a bit untidy so I went to 13.10. Eugh, it was like one of those horrible toolbars you see on friend's computers suggesting all sorts of wierd stuff. Well anyway, I thought a blank laptop would be an ideal opportunity to try out a distro I took a shine to a while back. I tuned into Sabayon to see what was new and gave their Gnome version a spin. Boy, am I impressed. It's a very pure distro, with (to my mind) no bad choices of apps or weird customisation. Hardware detection is spot-on, performance is good. It works out of the box, with all common codecs present and correct. The software repo is huge, not as big as the humongous Debian, and is very up-to-date. It's also a rolling distro, which means no version and precarious upgrades. The only thing I'm not used to is the package management. I'm used to apt and yum, but Sabayon's software is based on Gentoo. The GUI software installer, Rigo, seems nice and friendly, similar to Ubuntu but not quite as garish. I've been using it for a little while, and so far it doesn't seem to have any weaknesses. Give it a try - you'll like it. Sabayon | Home As for servers, I've used Centos, Debian and Ubuntu. Without doubt, Centos is the gold standard for reliability. It's ultra-conservative, and the software can be quite old, but it prizes reliability above all.

More signs you might enjoy...

The End of Britain - MoneyWeek Food for thought or sensationalist nonsense? Discuss.