setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
I can use all of those today or develop a new implementation if I want.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
He who controls the spice....
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Vendors come and go. Standards don't.
setq
|
8 years ago
|
on: Wikileaks reveals CIA's Elsa: a geo-location malware for WiFi / Windows
Isn't this the same principle google uses for their location services?
setq
|
8 years ago
|
on: Is it unethical for me to not tell my employer I've automated my job?
This sums it up nicely.
Also, if it's easy and you've done it a million times, charge an inflated fixed price. If it's new territory, charge by the hour.
Edit: before I forget, if you let them know how it's done then you need to charge for the several times they won't come back again afterwards.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
One doesn't win a game of chess by moving all the pieces at the same time.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Excellent. Downloading now :)
I ran NetBSD and OpenBSD on old sun kit in the late 1990s and early 2000's followed by Debian and then CentOS. FreeBSD got a look in persistently on the side. I'd rather like a step back to the sensibility of times past when you chucked something out and it just did its job until something blew up :)
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
This is interesting and lines up with the time zone offset on my last rant a couple of years back. Peak in upvotes UK afternoon followed by downvote pummelling at around 4pm UK time. Without wishing to don the tinfoil hat too much, actively squashing critical discussion on your product is a dick move if it's true.
This has got so bad on some parts of reddit they removed the voting buttons.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Interesting. I haven't used slackware for many years, so far back in fact that it had to come on CDs because I had a dial up. Will take a look in that direction this evening.
setq
|
8 years ago
|
on: Sorting 2 Tons of Lego, Many Questions, Results
That's really interesting actually. In the distant past I spent more time sorting the cards than playing the game so there is probably a good trade off on automating it.
I went and bought a duel deck the other day to play with the wife so this is going to become another issue in the future again.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Well no not really. Vulnerabilities exist outside the realms of the language implementations. There are poorly designed protocols and access controls to contend with as well. I'd argue there are a lot more of those classes of problems out there. The ones enabled by programming languages are merely easier to find as you don't have to understand the precise problem domain of the application for each one found.
setq
|
8 years ago
|
on: How Not to Encrypt a File – Courtesy of Microsoft
It's not. There's a content about 11 screens down, not that you'd find it easily.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
This is why we need standards and APIs which are immutable. It doesn't matter what the implementation is then.
The whole of systemd is a comedic fuck you to POSIX and the mentality of a system which is standardised.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
I apologise. This is the first time I've criticised systemd on HN. I had a massive rant on another site a couple of years ago when CentOS 7 dropped about the catalogue of failures I had been through with systemd, completely backed up with evidence and bug reports and it was hammered by downvotes instantly.
setq
|
8 years ago
|
on: How Not to Encrypt a File – Courtesy of Microsoft
setq
|
8 years ago
|
on: How Not to Encrypt a File – Courtesy of Microsoft
Most of the documentation is boilerplate. There's very little real content now and most of it is filler.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Indeed. Merely "loud" programmers with corporate backing.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Yes. I've burned hours on systemd related problems that just didn't exist before. From DBus message delivery failures, debugging things that haven't broken for 20 years (which has incidentally got MUCH harder) to the whole shit crock that is NTP and locale management. That and the whole desktop buggery that has been going on for the best part of 8 years now has really put me off. To be honest you haven't really experienced systemd's fuckery until you have a hosed box. It's like negotiating a boot with a pigeon. Any other platform is ZERO hassle and that includes windows, OSX, freebsd, openbsd etc.
And you can't criticise it anywhere (watch the downvotes).
The problem is it lacks the mysterious as in Zen and the Art of Motorcycle Maintenance class "quality". Merely glitter around a turd.
However we're stuck with it so it's suck it up or move on.
On the subject of moving on, you could run FreeBSD to run your servers. Much lower resource overheads, native ZFS, simple service management, some documentation worth more than toilet paper and the best thing of all, more sleep at night. Now there are binary updates and packages it's pretty easy. No more make world of any of that stuff.
setq
|
8 years ago
|
on: Ubuntu Systemd Vulnerability
Indeed. It's not just init, it's Windows service manager, COM, MSMQ, task scheduler and event log and all the associated problems in one convenient package for Linux!