harrytuttle

My main machine is a Lenovo T61 manufactured in 2006. My backup machine is a T400 from 2009. I have an HP48 manufactured in the mid 1990's still. All work perfectly.

2 years is taking the piss. Seriously. I feel people have been programmed into thinking this is acceptable.

From my perspective (I'm not the GP), I will be using a custom configuration management system that I wrote back in 1999. It's. Like puppet but ssh based, written in sh and standard Unix tooling. It doesn't use a DAG so you have to order dependencies carefully.

That will pull binary packages from ports builds on another machine and install and configure them.

Forgot about dtrace - good point!

So much goodness!

Not all batteries are made equal which is the problem.

We have 25 people with Lumia 820's that are fine. I just got a bad battery.

Downvoted by an Apple fanboy no doubt!

Well the main things for me are

1. feels closer to "old fashioned non-Canonical'ed UNIX" which I was brought up on.

2. Way less politics due to license.

3. Less crazy forking and wheel reinventing (basically everything Ubuntu isn't).

4. It has orders of magnitude better documentation

5. pkgng is actually really nice

6. separation of core OS vs ports/packages so easy to stage updates compared to catch all Linux distros.

7. pf is miles better than iptables

8. ZFS.

9. I have a Sun Ultra 30 sitting in my cupboard which Linux doens't like.

10. Has valgrind that works properly unlike the other BSD's.

That's about it but it's enough.

My use cases are: personal use, professional use (devops), professional use (production).

Well it's not comparable. I'm sitting on a new 9-cell that cost me $129 equivalent and has 8.5 hours left :)

When that runs out, I can take it out and stick the other one in out of my bag.

Wonderful!

I may actually consider dumping Debian for FreeBSD 10.

I've never been totally happy with Linux after moving off "proper" UNIX machines. I had a FreeBSD 4.4 machine floating around for years which I was rather happy with but drifted off to Linux-land primarily due to convenience when it came to Flash and audio.

So many compelling reasons to switch back to FreeBSD now.

If your Lumia's battery needed to be replaced after 9 months, it was already under warranty and should have been replaced by the manufacturer.

It was. Nokia service sent me a new one out for nothing after a 5 minute phone call.

You know what's also a safety nightmare? Batteries. Which is why stopping third-parties from replacing certified batteries with random bought-off-eBay batteries is definitely a good idea.

The problem is more power isolation. If you get a short when you damage the device etc (compression/impact/waterlogging), your typical LiPoly cell is going to catch fire or at least knock out extremes of heat. This is very hazardous. Removal batteries at least have a chance of power isolation.

My specific example here is my 2010 MBP which the battery was not glued (but inaccessible). This got waterlogged after a drink was spilled on the table. Turning it upside down revealed that capillary action around the base plate had sucked up the water. It rained on the logic board. About 30 seconds later, it caught fire. My only resort was to throw it in the garden and watch my £1249 investment burn up.

Apple does have a recycling programme where you can bring your old electronics for free

Yes they do but perhaps if you could replace the battery out of warranty, you wouldn't need to recycle it :)

Just because you can, doesn't mean it's right ;)

Nice work by the way. It's quite amazing the odd things you can do in Excel.

Yeah I know that. I buy T-series. No glue.

They're not a useful innovation - they are an abhorrent consumerist "disposalism" decision to pump sales, a safety nightmare (isolate it? nope), purely a cost cutting exercise for the manufacturer and make it even harder to recycle the nasty chemicals.

Don't give me the shit about it allowing smaller devices to be made either. You can make smaller devices with removable batteries fine.

I'm a qualified EE for ref.

Really like this when using the keyboard.

When using the mouse, the transition is implied so it's annoying.

Great work though!

What the hell? The M7 is a marketing label for some COTS silicon they licensed from some IP company somewhere (probably ARM/Broadcom or one of their associates).

It doesn't make unicorns shit rainbows or defy the laws of physics.

BBC did this 15 years ago on tiny computers compared to now. They uploaded static HTML onto Sun boxes and served them.

If you did a submission somewhere, it'd do offline processing and upload new static pages.

Most of this was C and perl.

No Scala, no Java, no Ruby.

iOS does HTML too you know.

I agree with the OP - most of this new technology doesn't really solve any problems. All it does is create an ecosystem you can feel superior being a member of.

Glue: technology shared with a $1000 and a $5 device but none in between.

I've just replaced the battery on my Lumia 820 after 9 months. They don't last forever. Glue is inexcusable. If they had a half decent mechanical design, foam pads would secure it in place when the device was assembled and allow replacement.

I'd probably buy new Apple products if they weren't held together with glue. I'm not investing lots of money in something intended to be disposable. My last MBP (2010) was at least servicable. Now replaced with Lenovo kit as it's possible to strip it down and replace anything.

Yes. Not like you can just nip to the Pegasus galaxy and nick a ZPM...

Well spotted! Thanks for pointing this out!

I will now go and hit myself with a LART for a bit to remember not to do that again.

"Bollocks"

peer reviewed demonstration or piss off.

Nice tools.

You can actually do most of that with vanilla PowerShell and Excel believe it or not but it's much fuglier and you spend most of your way working around edge cases.

The only thing that scares me about this though is that JSON is a terrible format for storing numbers in. There is no way of specifying a decimal type for example so aggregations and calculations have no implied precision past floating point values.

I would but if you see the rest of the thread, my gcc isn't raising this as a warning!

That in itself is sign that a mistake can be made without noticing.

I agree with you, but it works and it's saved me hours and hours of crying in front of gdb.

Thanks. I think this must be a config issue on this box. It makes me wonder what other warnings it is not telling me about.

Doesn't do that for me - what GCC ver and environment. Very odd! Digging in docs. Thanks for info.

What compiler flag is that? Genuinely interested. Wall,pedantic,ansi don't trigger it. I've tried the following and I don't get a warning or error:

   $ cat test2.c
   int main(int argc, char *argv[]) {
       if (argc = 0)
           return 1;
       return 0;
   }
   $ make test
   cc -Wall -ansi -pedantic    test.c   -o test

I thought that was system integration testing?

Huh?

   $ cat test.c
   int main(int argc, char *argv[]) {
       if (0 == argc)
           return 1;
       return 0;
   }
   $ CFLAGS="-Wall -ansi -pedantic" make test
   cc -Wall -ansi -pedantic    test.c   -o test

That's the failsafe (one I believe heavily in as well). But getting it right up front is still the best approach.

And this is why you write it like this when you use C:

   (0 == current->uid)

   (current->uid == 0) // or (current->uid = 0) in this case.

Would more code be more secure? To quote Theo de Raadt, who sums my opinion up nicely as well:

"You are absolutely deluded, if not stupid, if you think that a worldwide collection of software engineers who can't write operating systems or applications without security holes, can then turn around and suddenly write virtualization layers without security holes."

Quotas are easy enough to enforce. Most UNIX derivatives (including Linux) have disk and process quotas, some for over 3 decades.

Virtualization seems to be best used for reselling (and overselling) hosts that are smaller than the physical machine and not much else. Migration/failover is a non issue if you know what you are doing and if you need larger machines, it's just more overhead on top of a dedicated host. Plus it's increased administrative cost and more expense as a whole.

Yes but rationality and experience doesn't get you any upvotes in the tech communities. Raging fanboyism and denouncing the competition does.

Thanks for being rational - you are spot on.