Yeah, I had a similar Upbringing. We went out and just did whatever outside. Then back for Lunch and then out again. Running around in the woods, building dams in the small stream, and so on. We were at the fringe of a small suburban town right next to some woods. I think we also ranged about 1-1.5 Miles away from home. We did have some boundaries set up by our parents, but that was really more to kind of limit the places they needed to check whether we fell asleep somewhere or something. The area was certainly big enough and exciting enough to tide us over.
And when I was 11, I was given a card for public transportation and we went to school in the "big" city (biggest city in CH). We took public transportation, switched modes 2 times (10 min walking to the train station, 15 min train ride, 12 min tram ride, 20 min bus ride). After the initial confusion over how public transport works, where all the info is located at the stations, no big deal. We usually rode in a group of 2-3, but if you missed a connection, you'd ride alone.
I feel that Switzerland has (had? I don't have kids... no real idea how it is 20 years later) a healthy attitude towards this stuff. Maybe that's just because I grew up there, but I feel that having an environment where we feel that children can roam around without getting murderized at every corner is something all societies should strive towards. And this absurd helicopter parenting I hear about sounds like it's trying to mitigate symptoms, not alleviate the root cause.
CLA's are both good and bad. The good thing is that the software project has more flexibility when it comes to licenses, but the bad is that they have more flexibility when it comes to licenses...
The architecture might have been state of the art and completely reasonable back in "ye olden days". The fact remains that it's not appropriate for 2014.
If the reasons for this behemoth are compatibility with 50 years old processes, then these processes have to be modernized so this software can be scrapped. (or fixed, either way a huge project)
How so? So people can use Q's and Z's in their passwords? What would your business case look like? "Hey everybody let's spend $500 million so people can use arbitrary passwords, because [entropy], never mind most people use the name of their cat anyway?"
As ridiculous as that pitch might sound, it makes the implied security-money tradeoff directly visible to management and causes them to make a formal decision.
How so? if it's been used for 60 years, how many records do you think would be compromised if someone gained access to the system? Millions? Billions? Sounds like a good reason to 'modernize' to me.
The target breach would be nothing compared to the breach of a system in use for 60 years.
If their computer system is from the 1950's and they can't modernize it, why don't they also allow smoking and box cutters on the plane, and dress their stewardesses up all sexy?
Fortunately?? More often than we all care to admit, these things are exposed to the internet. (because it's so cool when I can turn on the coffee machine from my smartphone halfway home from work)
I understand what you mean. I had the same awe when I first started on Arch and really got to know all the bits and pieces. When I transitioned to systemd, I had to go through that again. It was actually very similar to what I did the first time around and I suggest you give it a shot too. systemd, while seemingly monolithic is actually a really cool suite of tools. The thing we need to keep in mind is that it's _not_ sysvinit, and it's not trying to be. It's trying to be a project that does more than that and does it transparently on all systems. You might like it :)
As a general point for everyone: Just because it's _also_ an init system doesn't mean it's not allowed to provide the binaries for doing a whole lot of other stuff. :)
The problem is that it's a suite of tools that are all developed under the same umbrella, by the same people, with the same ideas, and the same gatekeepers. It's rather difficult to fully replace parts of it, especially as the formal API to it is defined by systemd, and we're seeing more and more tools integrate with all that.
Why can't we have an independent organisation that defines a spec for all the relevant APIs and tools for managing a system, and systemd just be one implementation of that spec? Actually, it could be a suite of specs, so people could pick and choose which ones solve their problems, and build alternatives for others.
Hmmm... I pondered this for a bit, and I arrived here:
> [...] by the same people, with the same ideas, and the same gatekeepers [...]
Isn't this exactly what made the Linux Kernel great? A consistent vision.
I agree with you on a few points though, the systemd team should be more cooperative and start being conservative on the API changes. If the API is defined clearly, it shouldn't be hard to make proper replacements for parts of it.
I disagree strongly that there should be an independent Organisation to define that spec, because that would quickly be overrun by bikeshedding and all the other problems stemming from design by comittee. Very often in the Open Source world, specs have been defined by the first people arriving at the scene, so to speak. It all works over dbus, no? That is a fairly simple protocol to implement. I think it's an elegant IPC solution.
> Isn't this exactly what made the Linux Kernel great? A consistent vision.
Sure, but even today, the Linux kernel has competition. I can run most things on Windows or OSX or FreeBSD or Solaris, even if the technical details are different. I worry about a monoculture forming around systemd, as seems to be happening now; I can't find a modern distro that uses anything else (aside from Gentoo, which I can't take seriously for production work), and it's starting to be assumed that systemd is the only init system that anybody will use.
If these were all EFI/UEFI machines, there is a lot more code in these preboot EFI environments than one expects. Room enough to hide this kind of payload.
I could expect ONLY the DSP, ONLY the windows-individual portion, maybe 4 or 5 BIOS exploits and maybe 2 or 3 BIOS patches, about the same for Ethernet cards, maybe the CD controller, maybe 1 or two different USB firmware exploits and patches, maybe the entire PSU manipulation logic
but ALL of that? In the BIOS?
(I'd like to point out I am nowhere near the caliber of the man who's supposedly experiencing all of this. I do not know the true size of any of the aforementioned payload.)
With UEFI/EFI it's pretty plausible that you can load additional code at runtime from elsewhere even outside of the large space available for UEFI/EFI itself. Some versions even self contain quick booting minimal environments that contain web browsers and such.
I think they mean to say it was a computer that was previously infected and then airgapped, wiped and reinstalled. But because the executable load is in the bios, it persisted and reestablished communication with its peer via HF audio.
Yeah, I had a similar Upbringing. We went out and just did whatever outside. Then back for Lunch and then out again. Running around in the woods, building dams in the small stream, and so on. We were at the fringe of a small suburban town right next to some woods. I think we also ranged about 1-1.5 Miles away from home. We did have some boundaries set up by our parents, but that was really more to kind of limit the places they needed to check whether we fell asleep somewhere or something. The area was certainly big enough and exciting enough to tide us over.
And when I was 11, I was given a card for public transportation and we went to school in the "big" city (biggest city in CH). We took public transportation, switched modes 2 times (10 min walking to the train station, 15 min train ride, 12 min tram ride, 20 min bus ride). After the initial confusion over how public transport works, where all the info is located at the stations, no big deal. We usually rode in a group of 2-3, but if you missed a connection, you'd ride alone.
I feel that Switzerland has (had? I don't have kids... no real idea how it is 20 years later) a healthy attitude towards this stuff. Maybe that's just because I grew up there, but I feel that having an environment where we feel that children can roam around without getting murderized at every corner is something all societies should strive towards. And this absurd helicopter parenting I hear about sounds like it's trying to mitigate symptoms, not alleviate the root cause.