Re: 3 seconds
Patrick, is that you? Better scan the Zagat for somewhere else to go...
614 posts • joined 11 Jun 2009
At university I was finding out the hard way that maybe I wasn't cut out to be a programmer (am now a sys admin). Part of that voyage of discovery was the first year exams, one of which was pretty much designing and coding on paper for 3 hours. I think I got an E for that one. I wasn't the greatest fan of having to do something rather computer-centric, without an actual computer. Aside, yes I know in the very old days that's how people did stuff, but I'm pretty sure we'd moved on from that in the 1990s.
On the flip side to all this it's obvious that the coursework element to such a subject, moreso when it is actually coding, is just far to easy to subvert via a multitude of methods. Quite what the best answer to this problem is I'm not sure. I guess there is the concept of coding within a time limit in some sort of closed condtions, though I've managed to screw up such things myself too (the pressure, the pressure!).
Me too. My 6S was the first new handset I purchased (the rest have been hand-me-downs from brother, 2nd hand from fleaBay or work devices). My days of wanting the latest tech shiny are not what they were and as far as I'm concerned my 6S does everything I want it to. So no point in upgrading. And even then I really don't like how the iPhone has evolved. No 3.5mm jack and a move from fingerprint scanning to facial recognition do not fill me with joy.
On subject when I saw that Apple were offering a new battery (all kosher with warranty etc) for £25 I jumped at the chance. The previous battery was still OK, but a slight bit of preventive maintenance never hurts.
So this will delay me in purchasing a new iPhone, but if Apple/industry/analysts/shareholders think I'm going to buy a new device ever year "because", they are sadly mistaken. For all Apple's problems, "innovations", lack of upgradability/fixing and dumbing-down, they do generally tend to make kit that not only physically lasts, but is supported too.
^ Dear $deity this! That's probably my biggest complaint about systemd. So when I change the config of something then start the service if if bombs out just show me the bloody error message!
But no, we have to use another util which mostly tells you sod all about what really went wrong and you have to hunt around for the original command, then run that yourself just to see the actual error message.
Work mobile on O2 and my own on GiffGaff. So no data for me. Though I'm stuck in an office all day with web and wifi, so not the end of the world. Though the lack of calls/texts earlier was somewhat annoying.
I now await the examples of rage from users on Twitter who have based their entire existence on O2 infrastructure... If it's that important, have some sort of backup.
I recall another commenter saying something along the lines of "dross in 3D is still dross".
The move to HD got the TV manufacturers all excited that they could flog more kit if they just threw a new bit of tech in. They conviniently overlooked that SD->HD was quite a useful jump as not only did it look good, but there was increasing content and the not-so small factor that many people don't change TVs every few years (my previous TV was 9 years old). So then we see them bigging up 3D, curved screens, smart TVs etc
Anyway, back on subject. Dross in VR is still dross.
I'm amused that it's marketed at people so stupid that need a reminder to stand up. I may have a bit of Apple kit about, but I'm still completely unconvinced by the Apple Watch. Plus I've got a perfectly good watch that doesn't need recharging every few days or some sort of mobile connectivity to work properly.
Maybe they should constantly play Marillion's nice tune at him until he decides that he doesn't want to be incommunicado any more and so exits his broom cupboard and embassy by choice to get some of that lovely wifi.
Though it may be a brief flirtation as I don't think the Met or HMP offer wifi either....
I must have been one of the lucky ones, I managed to log in around 1630 yesterday. Fortunately for me it's not my main account. Though there must be quite a bit still broken as before the big debacle if you already had an account you could apply for others online. After the debacle that all stopped ("coming soon") and it's only recently that they've started to allow online applications again for some account types.
As I'm a bit of a rate tart, then I've got quite a few accounts from different providers. It may pain me to say it, but TSB's front end is a lot better (eg clean and easy to navigate) than some of its competitors.
I agree. Though in some cases there is a catch. It looks like Dell put custom firmware on their own-branded SSDs. So if you use a non-Dell SSD (even one from an approved 3rd party reseller), then the lack of that custom firmware will result in the drive showing up with a non-critical error. It works fine, but doesn't help with hardware reporting.
Interesting, as I've pretty much had the opposite experience. Maybe it's because our account manger is a perfectionist, but I've never had any big problems. As I've said before in comments somewhere they put the value add into VAR for us. Mind you, some of their competitors don't help themsleves with not being able to correctly read emails with server specs in them or taking days to provide a quote.
I've had that too many times! Namely trying on a suit is MossBross, wearing a green Classic Team Lotus fleece in some DIY place, wearing an UMBRO top in some sports store and the worst of all being wearing a yellow Classic Team Lotus polo shirt in Ikea (where I was collared about 3 times).
I can't remember if it's HPE or Dell (or both) where you can use set the kernel option biosdevname=0 during build/boot to turn all that renaming stuff off and revert to ethX.
However on (RHEL?)/CentOS 7 I've found that if you build a server like that, and then try to renam/swap the interfaces it will refuse point blank to allow you to swap the interfaces round so that something else can be eth0. In the end we just gave up and renamed everything lanX instead which it was quite happy with.
Ah yes, another systemd (RHEL?) annoyance in that by default the actual rc.local script is not set to be executable and that rc-local.service is disabled. It's almost as if someone doesn't want you to be using it.
Also in systemd, rc.local is no longer the last script/thing to be run. So in order to fudge something to work in rc.local I had to create an override module for rc-local.service that has a dependancy on the network being up before it runs.
I can see some (well, one) benefit of systemd in the depandancies. So things may only start when a pre-requisite has been met.
Unfortunately that is outwighed by the annoyances. For me the worst is stuffing everything in a binary log and not telling you any error message when you restart the service. So you have to go hunting for an error message and in some cases just end up running manually what the service was meant to do just to see what it's complaining about. It's time I'd rather spend fixing the problem itself.
Like other commenters I tolerate systemd as it's part of RHEL/CentOS/Oracle Linux etc 7.x and that's what we have to use. Obviously that's no endoresement.
Last year we needed to plonk an NTP server somewhere until we got out new time infrastructure in. Somewhat jokingly boss of boss suggested an RasPi. I thought about it and realised that it wasn't such a silly idea. So we purchased two (always have a backup!), threw on CentOS 7 (so they fit in with everything else) and aside from a USB dongle on one of them playing silly they worked fine for several months.
Once they were decommed from that use I took one home, threw on RiPTC and now use it as a VMware Horizon thin client to connect to work.
My first proper job, I was on the console of a test server (running UNIX) which I needed to reboot. So I typed in the shutdown command, pressed return and then wondered why instead of seeing the running commentary of the server shutting its services down I was faced with a disconnected telnet session message and the prompt of the test server...
...I then realised one of my collegues has rather stupidly logged into the prod server on the test server's console. So I'd just rebooted the prod server, as stupidly for me I hadn't checked whoch server I was typing the command on. I got away with it as we were a bit of a law unto ourselves, it was a stunningly good education of how not to run a data centre. Once I moved elsewhere I realised things were very different!
Similarly in reverse I sometimes buy eBooks from Kobo, which are in EPUB format. In order to read them on my suitably old and creaky Kindle (which is MOBI or AZW only) then I load them into Calibre, strip the DRM out and convert them to MOBI. Somewhat annoying that I have to hoist the skull and crossbones flag etc in order to consume a legally purchased item.
Historically I've avoided buying from the Kindle store as the eBooks were locked to the Amazon account used to purchased them and were infested with DRM. Ironically I prefer to buy music from Amazon as it's in MP3, though it's been quite a while since Apple's AAC (or whatever it is) had DRM.
Can't agree enough. I commented at the time that no good would come of having three different (and non-compatible) products called Windows 8 and sharing the same interface. An interface that was an OK idea on touch devices, but was stunningly un-suited to a traditional keyboard/mouse setup. The most stupid thing is that as soon as the public saw/used Windows 8 on a PC in test/beta they said it was shit and Microsoft decided they were all wrong and continued as planned.
Windows 8 x86/x64 != Windows 8 RT != Windows Mobile 8 (or whatever it was called)
From my experience (as a security-minded sys admin) security isn't anywhere on the radar/horizon of DevOps types. They think it's quite normal to drag in who-knows-what from the outside world to use every five mins. And then once it's in they'll have a long list of complaints that they can't do X, Y and Z because our (sane) security policies forbit it or that they've implemented something which doesn't conform to anything else we have.
On the subject of email clients I use Thunderbird on the Mac (s'OK I suppose) and Spark on the iOS stuff. Any of the default Apple mail clients drive me to distraction when I try to set them up as they constantly try and second guess what they think I'm after. Just let me put in all the sodding config myself then test it!
For my sins at work we've got Lotus Notes, of which the saving graces are that it's not as bad as it used to be and it's not actaually a dedicated emaul client as it does loads of other stuff too.
It doesn't give off the impression that their setup/kit/etc is ideal. Things happen, but you shouldn't really ever be in the position of having a disk fail in a RAID 10 to cause such an outage. If it was multiple disks, then either someone wasn't monitoring or they used crappy disks (no excuse for either if hosting is your business!). And that's before you even mention the fact that their estate doesn't seem to support moving virtual machines to other hardware as other commenters have mentioned.
The only bit I have empathy with is when a disk goes, the RAID controller does its best, but a filesystem makes itself read-only until you can run an fsck/check. But still, at worst that's a reboot and a few hours. And if your business is hosting, you should be able to withstand a piece of physical hardware breaking.
One slight problem for the consumer is that with a dish, things are relatively easy to troubleshoot for the engineer who will come round (dish, LNB, cable, STB). However if it's all over broadband then there's bound to be the usual (ISPesque) fobbing off that the problem is almost definatley not with Sky, but elsewhere. So in the worst case you'll have to juggle both Sky and your ISP to sort things out. On an equally bad case then Sky may be your ISP. And then throw in the entire BT/OpenReach thing that the ISP should be doing.
I'm sure it'll be mainly fine when it's all running, but wouldn't like to be around when something goes wrong.
Biting the hand that feeds IT © 1998–2019