Show us the source, ASUS
By not providing source for software which is distributed under licences such as the GPL, they're breaking the licence conditions and, as a result, they do not have permission to distribute the binaries.
283 posts • joined 14 Dec 2007
“… I think it would be an excellent idea if people were charged to receive emails. Say 5 pence each.”
Your proposed charge would cost me 50p or so already today, and that's just for the spam which escaped my ISP's filters. I'm on several mailing lists, and some of them are moderately active; your charge would cost me several £ per day.
So, unless you're willing to pay for all email which I receive, you can stick your excellent idea where the sun doesn't shine.
No idea about ATIs driver's since I use open-source driver's. The card's seem fine to me, though Ive been careful to pick one's which are supported (thing's are definitely improving in that respect). Intel graphic's hw tend's to be a bit slow but fine otherwise (curiously, faster for Xv textured video than the oldish-but-fast-enough ATI hw that I use), and nVidia… no, I refuse to be limited to whatever kernel version's they support, so Im completely unaffected by this problem :-)
Mines the one on the apostrophe-shaped hook.
DVB-T via PCI card or USB stick:
✓ HD ‒ at least if it's handed off to the CPU or graphics hardware for decoding, and the hardware is fast enough.
✗ DVB-T2 – unless the packaging specifically mentions it, it's safest to assume that the device can't handle it.
✓ 64QAM ‒ in use, and we have some muxes using 16QAM: instant 30% capacity increase (two more shopping channels!) on those muxes when they're switched over…
⚠ 8k mode ‒ my DVB-T PCI cards don't seem to support this (they're not exactly current models, though), but it seems that my DVB-T USB stick does.
Years ago, supermarkets used to recycle their recently-emptied cardboard boxes by making them available for customers to fill with their shopping, and some would be re-used again at home.
Perhaps we should go back to that…
And as for packaging: agreed. Far too much of it, though it's not just the quantity and the size relative to the (useful) content – much of it isn't really reusable.
Yes, break them up :-)
“So do we really have 3,5 billion used ip addresses - or just a hell of a lot of slack space?”
More like 3.5 milliard, but there probably *is* a lot of slack.
“Some companies give you 8 addresses, even if you only need 2 or 3.”
And for good reason: if they hand you a /30 rather than a /29, you get only two useable out of four rather than 6 out of 8.
(It's a little bit unfortunate that, many years ago, one group of people used the first address in a block as the broadcast address and another group used the last address, and we all ended up with two unuseable addresses per block rather than one…)
Depends. You see, there's this nice 'from=' option which you can apply to individual keys in your authorized_keys; and if you're using that (ooh, static IP, shiny), you're a bit more secure even with a weakly-generated key since it'd require more effort from the attacker.
I'd still replace any weak keys.
“well i've submitted a question for tonights Question Time. … I'm sure it will be ignored and they will be asked about the health of gordon Browns dog instead, ho hum”
Yes, it got ignored (or at least not used), and the metaphorical question about Brownjob's dog was indeed asked.
Biting the hand that feeds IT © 1998–2019