FreeSync/G-Sync makes a tremendous difference, but unfortunately does this to the price as well :(
Edit: Or you can use a CRT :)
166 karma · joined April 25, 2009
FreeSync/G-Sync makes a tremendous difference, but unfortunately does this to the price as well :(
Edit: Or you can use a CRT :)
UK Freeview HD is 1080i though, but it's in a very bandwidth-inefficient container as it's just the transport stream which is sent over the network. I've also played some 1080p content over it with no problem, but most of the content I use is 1080i.
No idea how old my wiring is (house is from 1950), and this is across the distribution board / fuse box too, as it's between upstairs and downstairs in my house. So my experience is completely different to yours and much more positive :)
Do you not feel it makes you more likely to have an accident?
The former isn't something which is happening yet anywhere that I know of (in the UK at least, even in new-build houses), and the latter needs pressure from consumers which isn't happening for anything in the internet-of-things space yet :/
(edit: don't try to use markdown in HN comments, however automatic it has become for you :)
(I've not used it so I couldn't say why)
RF spewing out of the mains wiring is true, but again I've not had any obvious problems due to this. (I'm surprised that they're allowed to be used despite this, however)
edit: Streaming TV over it in that I use it to connect between a MythTV front and back-end, and haven't had any connection or bandwidth issues that I've noticed. It's been pretty rock-solid for me :)
(Does kdbus count?)
Where do you draw the line between it being the corporation's fault and the individual?
(I suspect these questions are part of the reason it is the way it is currently)
At least the AMD Bulldozer architecture diagram on the Wikipedia NUMA page shows this, both within a socket and between sockets:
https://en.wikipedia.org/wiki/Non-uniform_memory_access#/med...
Is the same true for Intel chips? (The Wikipedia page mentions the Intel E8870 memory controller, but not whether newer chips use similar set-ups)
Having a separate wifi network (and separate VLAN for wired) IoT devices sounds like a good idea, and is something that I'll be doing this weekend...
(Also will port-scan the MiLight bridge to see if it's got any other interesting services on it)
I find the same with virtually all animations on phones and other UIs. If it can show me what I want a smidgen quicker by not animating then it gets disabled.
I have just done this myself with a 24-month contract saving 6 GBP a month (making it 4 GBP a month, including 500Mb/month of data) which paid for a Milestone 2...
Still, the current standard says it's not legal so it seems like a bad idea to rely on undefined behaviour...
This is not valid C usage of unions. They are _only_ for use as a method to save space, not for conversion between types, despite it being a very common usage of unions.
This can cause all manner of problems when compiler optimizations such as type-based alias analysis are used.
EDIT: Turns out I'm completely wrong on this and it's fine from C99 onwards.
I recommended them to several friends and colleagues, but from what I've seen of Rackspaces offering I wouldn't be able to do that with them.
RIP Slicehost :(
They have static ("Elastic") IP addresses:
http://aws.amazon.com/articles/1346?_encoding=UTF8&jiveR...
..don't these let you keep the same IP for your Puppet master instance?
This means that you lose a large amount of the power of using puppet, by which you can use configurations across machines to do things like collect up all the services you run on a set of machines and generate a nagios config, or firewall config, or whatever. Without using stored configs for this I assume it's possible but will require more explicit configuration rather than the rather more elegant solution provided when using a puppet server.
Side note : I've used puppet on a fairly small scale of up to ~50 machines, and just started using it for VMs, and it's pretty straightforward to integrate into a bootstrap install to get ruby and puppet installed so that you can use it to install all the rest of the dependencies. But of course, the most use is for changes later on rather than at install-time when there are already a huge number of tools to set up or image machines or whatever.
Side side note : I've not used Chef to compare this with.
Clearly no-one in the US gets any text message spam, or they'd be _really_ angry about paying to receive that.
I'd say that it's more that if there's no (current) way to track what the other package management system is doing on the distro (any distro, not just Debian) then they can't tell what packages are installed and hence whether the distro-supplied packages can work with them...
Absolutely, but this problem has been around for a long time, and fighting with distributions on how to get it to work won't help anyone.
Of course, it also means that if you install a buggy version of a library from, say, CPAN then you could break distro-supplied packages... I guess it depends on which you value more: distributor-provided testing or being able to install out-of-band packages onto your distribution more easily and with proper dependencies.
IME, separate package-management for each and every language is more painful than the problem he is describing.
Rubygems, CPAN, whatever other languages use.
As soon as you install things outside of the distro package-manager, it has no idea what is going on with those packages and so continues to think that they aren't installed. If there was a way to get the package-managers for language libraries and the distro to play together nicely and work for dependencies etc then this would be OK, but as it is it's a bit of a sysadmin nightmare.
Edit: I thought that installing distro-supplied packages into /usr/local was against the FHS?
So reboot -> no loop protection and that 3-cable LACP trunk I'd just put them on was suddenly a bit of a loop[1]...
Moral of the story : Don't assume that (what seems like) a minor version update in a product doesn't change the behaviour substantially (the 1800G switches save the config when you make changes, the 1810Gs have it as an explicit step).
[1] A gigabit loop on a completely flat network, so there was essentially a gigabit of broadcast traffic pounding at the ~100 machines on the network...
rpm -e *
..which had much the same effect (and no confirmations required!)