Broadcom has actually pretty much worked themselves into a niche that they are quickly being competed out of. Their shitty business practices are sealing their fate.
Non-BCM routers and network hardware are becoming more and more prevalent.
Parent is right, broadcom is dying.
Well, to be fair, the secure bootloader is only enabled on Secure parts, which you don't have (unless you got them on a phone, or some such device that ships with them).
On a non-secure part, the secure-bootloader documentation is irrelevant.
While it does suck that the average hacker doesn't have access to those docs (especially when we're fighting against beating the secure bootloader in shipped devices), one can hardly claim TI provides shitty docs because of the omission.
You've got good ground to stand on in the SGX department, however.
There's no arguing the RPi's incredible mind-share, but I still contend that the market minus the Pi isn't really much different than it was before the Pi. More people have just been brought into it. I don't see more choice than I saw before, or better prices. I think what the Pi brought to the table was a bunch of people who weren't willing to spend more than $35 on SBC toys. I don't love or hate the Pi. I have 2 of them, and an ODROID-W (yay, on-topic!). It's one of my lower-end SBC hobbyist boards, but definitely not at all bad for the price. I still consider the BBB a better board by a large margin for $20 more (used to be $10 more).
Galileo is an Arduino compatible board that uses the Quark SOC.
It's also the only hobbyist board the quark ships on. (that's available to the public).
Intel doesn't really have a competitor to the Pi, though I do expect that to change eventually. (Quark will not be the chip to do it- any competitor will need a GPU)
They did get an initial batch made apparently, because ODROID-W arrived in the mail last week. I like it far better than my RPis. Very small form factor, without all the stuff on the RPi board that I don't need. It's a shame it's being cancelled.
Pretty sure the Arduino market is what pulled Intel in. http://arduino.cc/en/ArduinoCe...
And you know... You may be right. There was no embedded SBC market before the Pi came out.
The Pi competed on one front, and one front only. Price. And no one really competed with it. The boards of similar (but still higher) price that destroyed the Pi in functionality were around before the Pi was.
It's not a treaty to be honored. It's a signing statement to the accession of Ukraine to the NNPT. While gentlemen could be expected to adhere to their weak promise, it's not some ratified-into-law agreement signed by all parties. Attempt at misinformation, or ignorance? Be honest.
but I am sure that starting a nuclear war, without the permission of socialist Britain, on the doorstep of the 2 biggest and most anti-American military forces on the planet would have destroyed the USA.
Pretty unlikely. Keep in mind the time-frame. Korean war. Pre-Chinese nuclear capabilities, and pre-ICBM. Russia sure as shit wasn't gonna fly bombers over and (try to) nuke us for blowing up Chinese regulars crossing the border... Not that I'm remotely in favor of doing something that vile.
One could call it a limitation, but it's also manifestation of the UNIX security model.
Any random Joe Schmuck can also make a required change to the blinkenlightsd init script to programmatically alter its startup characteristics to fit his unique system startup requirements. He can't do that with systemd. I call that a limitation. So what we're really arguing is whether or not the status quo limitations are less important than the new limitations you want to introduce.
Humorously, back in my IOS hacking days, (original iPhone), where we were altering kernel pagetables to map hardware into userspace processes and dump bootroms, trying to fix startup inconsistencies related to our limited ability for changes, and the fucking disgusting web of unnecessary cross-dependencies that the boot process practically begged be used, launchd was the second-stupidest feature of that operating system I noted. It's not a real surprise that a lot of people have jumped on the "Apple's way is the best way!" bandwagon, really. Half the people maintaining distros these days see Apple as some kind of thing to look up to, in spite of all available market evidence. I can only surmise that it has something to do with upbringing/education.
Entirely false. In an environment with ~400 servers, it's not remotely close to a full-time job. For services that suck or are prone to crashing (very, very few on our deployments) an inittab restart directive does the trick, or for things that are prone to hanging and going full retard, monit does the trick.
You know what sucks my ass though? Not being able to modify the init scripts as I need. I'm so glad we've made a daemon that will make sure I never need to alter the low-level starting dynamics of a service again. At least I assume it does that, since it *does* deprive me of my ability to.
run a process that does heavy syslogging to the tune of 25-30K messages per second. Yes, its bad app design but come on - this thing worked for years and now its suddenly broken???
Using the syslog facility is not bad app design. In a world where you're subject to the limitations of systemd, it is indeed poor design, but it wasn't. Systemd is broken, not that app's design.
Well, generally when programs require privileged ports, they must be run as root- and then they drop privileges.
It's kinda been that way since... well, forever. I'm sorry you're so late to the party.
Also, you should talk to your distribution's BIND maintainer about his shitty init scripts.
The 2nd most used Unix is OSX. That uses launchd. That of course handles the problem of integrating in daemon tools and cron like features into the launch system which is different than either init or systemd. If the goal were better compatibility with other Unixes that not init would be the target.
That's like arguing that all V8s should use cam-in-block architecture because GM uses them.
Why? A restart of the service may very well clear out any logs relevant to the crash.
You wrote some pretty poor daemons. Since you can't be bothered to use the syslog facility, my suggestion is that you start opening files without calling truncate on them after.
Your point?
I don't recall those scientists screaming from the top of their lungs that if we didn't build bombs, experiment on prisoners, be racist nazi shitbags, or any other horrible things, then we were going to irreversibly fuck this planet up (for any time scale that is relevant to our civilization, thereafter)
The fact that some scientists have flexible morals shouldn't be made equivalent to the fact that corporations have entirely inflexible null morals.
I never debated those things, why did you bring them up?;)
Slashdot Mirror
Broadcom has actually pretty much worked themselves into a niche that they are quickly being competed out of. Their shitty business practices are sealing their fate.
Non-BCM routers and network hardware are becoming more and more prevalent.
Parent is right, broadcom is dying.
Well, to be fair, the secure bootloader is only enabled on Secure parts, which you don't have (unless you got them on a phone, or some such device that ships with them).
On a non-secure part, the secure-bootloader documentation is irrelevant.
While it does suck that the average hacker doesn't have access to those docs (especially when we're fighting against beating the secure bootloader in shipped devices), one can hardly claim TI provides shitty docs because of the omission.
You've got good ground to stand on in the SGX department, however.
I'm a long-time Olimex customer... From back when ARM7 (not ARMv7) was the rage. Great company, great products.
There's no arguing the RPi's incredible mind-share, but I still contend that the market minus the Pi isn't really much different than it was before the Pi. More people have just been brought into it. I don't see more choice than I saw before, or better prices. I think what the Pi brought to the table was a bunch of people who weren't willing to spend more than $35 on SBC toys. I don't love or hate the Pi. I have 2 of them, and an ODROID-W (yay, on-topic!). It's one of my lower-end SBC hobbyist boards, but definitely not at all bad for the price. I still consider the BBB a better board by a large margin for $20 more (used to be $10 more).
Galileo is an Arduino compatible board that uses the Quark SOC.
It's also the only hobbyist board the quark ships on. (that's available to the public).
Intel doesn't really have a competitor to the Pi, though I do expect that to change eventually. (Quark will not be the chip to do it- any competitor will need a GPU)
They did get an initial batch made apparently, because ODROID-W arrived in the mail last week. I like it far better than my RPis. Very small form factor, without all the stuff on the RPi board that I don't need. It's a shame it's being cancelled.
I just got my ODROID-W! That's really sad to hear it's discontinued. It's a sexy little board.
Pretty sure the Arduino market is what pulled Intel in. http://arduino.cc/en/ArduinoCe...
And you know... You may be right. There was no embedded SBC market before the Pi came out.
The Pi competed on one front, and one front only. Price. And no one really competed with it. The boards of similar (but still higher) price that destroyed the Pi in functionality were around before the Pi was.
It's not a treaty to be honored. It's a signing statement to the accession of Ukraine to the NNPT. While gentlemen could be expected to adhere to their weak promise, it's not some ratified-into-law agreement signed by all parties. Attempt at misinformation, or ignorance? Be honest.
Oh, I'm pretty sure the Kennedy doctrine was falsified the second we got involved in Vietnam and propped up a murderous dictator.
but I am sure that starting a nuclear war, without the permission of socialist Britain, on the doorstep of the 2 biggest and most anti-American military forces on the planet would have destroyed the USA.
Pretty unlikely. Keep in mind the time-frame. Korean war. Pre-Chinese nuclear capabilities, and pre-ICBM. Russia sure as shit wasn't gonna fly bombers over and (try to) nuke us for blowing up Chinese regulars crossing the border... Not that I'm remotely in favor of doing something that vile.
You're not. The definition of "holographic" has been usurped by Star Trek.
One could call it a limitation, but it's also manifestation of the UNIX security model.
Any random Joe Schmuck can also make a required change to the blinkenlightsd init script to programmatically alter its startup characteristics to fit his unique system startup requirements. He can't do that with systemd. I call that a limitation. So what we're really arguing is whether or not the status quo limitations are less important than the new limitations you want to introduce.
It would probably depend a lot on whether or not I really was an asshole
Yes. Admittedly, rarely, and it's a perk, not a requirement.
Humorously, back in my IOS hacking days, (original iPhone), where we were altering kernel pagetables to map hardware into userspace processes and dump bootroms, trying to fix startup inconsistencies related to our limited ability for changes, and the fucking disgusting web of unnecessary cross-dependencies that the boot process practically begged be used, launchd was the second-stupidest feature of that operating system I noted. It's not a real surprise that a lot of people have jumped on the "Apple's way is the best way!" bandwagon, really. Half the people maintaining distros these days see Apple as some kind of thing to look up to, in spite of all available market evidence. I can only surmise that it has something to do with upbringing/education.
Entirely false. In an environment with ~400 servers, it's not remotely close to a full-time job. For services that suck or are prone to crashing (very, very few on our deployments) an inittab restart directive does the trick, or for things that are prone to hanging and going full retard, monit does the trick.
You know what sucks my ass though? Not being able to modify the init scripts as I need. I'm so glad we've made a daemon that will make sure I never need to alter the low-level starting dynamics of a service again. At least I assume it does that, since it *does* deprive me of my ability to.
run a process that does heavy syslogging to the tune of 25-30K messages per second. Yes, its bad app design but come on - this thing worked for years and now its suddenly broken???
Using the syslog facility is not bad app design. In a world where you're subject to the limitations of systemd, it is indeed poor design, but it wasn't. Systemd is broken, not that app's design.
Well, generally when programs require privileged ports, they must be run as root- and then they drop privileges.
It's kinda been that way since... well, forever. I'm sorry you're so late to the party.
Also, you should talk to your distribution's BIND maintainer about his shitty init scripts.
* CAP_NET_BIND_SERVICE notwithstanding.
The 2nd most used Unix is OSX. That uses launchd. That of course handles the problem of integrating in daemon tools and cron like features into the launch system which is different than either init or systemd. If the goal were better compatibility with other Unixes that not init would be the target.
That's like arguing that all V8s should use cam-in-block architecture because GM uses them.
Seems legit.
Is this a trick question?
Why? A restart of the service may very well clear out any logs relevant to the crash.
You wrote some pretty poor daemons. Since you can't be bothered to use the syslog facility, my suggestion is that you start opening files without calling truncate on them after.
I apologize, I was answering the hypothetical answer to the GPs question... You know, the one you didn't actually answer.
Ya me too, I much prefer a climate that we're not evolved to survive in. Humanity sure flourished through the Dryas events, didn't they?
Your point?
;)
I don't recall those scientists screaming from the top of their lungs that if we didn't build bombs, experiment on prisoners, be racist nazi shitbags, or any other horrible things, then we were going to irreversibly fuck this planet up (for any time scale that is relevant to our civilization, thereafter)
The fact that some scientists have flexible morals shouldn't be made equivalent to the fact that corporations have entirely inflexible null morals.
I never debated those things, why did you bring them up?
Fuck, that was heart breaking to read.
With enough energy, we could fly to Alpha Centauri A in 1 minute and 15 seconds.
I'm glad we did this exercise.