bumping some orbital body large enough to obliterate the area in question and small enough not to destroy the planet's surface. You would classify it enough so that some of your own people would die so that you could bond with the natives in a shared experience of grief, tell them that the area is dangerous and that by stretching our own meager resources we might have the equipment to render the area safe again, one day. In the meantime we can only protect you natives if you stay away from the area.
Why the fuck would you risk your own assets when you can control what falls on where from orbit and no one can see your preparations and planning. In that regard Avatar is more stupid than a bunch of Jar Jar Binks.
You are nothing like the airline industry who actually is a learning industry. You've learned how to PR spin and do the absolute minimum you have to do. You do the same arrogant dismissal of people's concerns and treat them like they are stupid. Fukushima proved the Nuclear Industry learned nothing from Chernobyl except how to better cover evidence and ensure the flow of information is stifled.
I used to support nuclear power, I thought it would save the world and the more I learned and asked questions the more I got labelled as "anti" unclear power.
Indeed it is this very conceit that you demonstrate that is cited in the Official report on the Fukushima accident as a key reason why Japan's unclear industry "managed to avoid absorbing the critical lessons learned from Three Mile Island and Chernobyl" and "how it became accepted practice to resist regulatory pressure and cover up small-scale accidents" like we see here.
The last thing it says about this conceited attitude is: "It was this mindset that led to the disaster at the Fukushima Daiichi Nuclear Plant. "
The attitude you display, as a professional, is no different and is a clear demonstration that the only thing you've learned from Fukushima is to point fingers and say "Not our problem".
You are never going to see another Chernobyl, what they did was just crazy. Three mile island? we've learned from that, we have procedures in place, we have training in place, we believe what our instruments are telling us and we take action to deal with the anomaly. Fukushima? yeah we've learned about the vulnerabilities with that too and made improvements to deal with a total station blackout.
The vulnerabilities at the Fukushima reactors were well know for decades before and GE issued procedures for ensuring that those situations would not arise for that generation reactor. The operators did not take sufficient measures to protect the reactor or the community around it.
Everything that happened in that accident was predicted by the American Society of Mechanical Engineers from an un- fuelled pressure test of that generation reactor because it was those results that led GE to devise those condition to mitigate the basis design issues that they uncovered.
Those factors were not taken seriously enough by TEPCO and that is what led to the accident.
When Nuclear power fails you people claim that no one dies whilst it obliterates communities. Fukushima province was destroyed by a Tsunami however the reason it's people can't return *home* and rebuild is because a nuclear reactor spewed radioactive isotopes all over the place where that community used to exist. The same thing happened at Chernobyl.
But you guys can never take responsibility for anything, minimize everything, attack anyone who has their own concerns no matter how valid and no one has any choice but to accept that unclear power is there.
It would be great if we could get new designs approved that are failsafe but since the climate in North America for nuclear is cold, we deal with the old designs. They really do work well.
They may work well. What we have learned is that human organizational systems are not mature enough to handle nuclear power safely. Commercial reactors that are operated by for profit operators have demonstrated an unwillingness to pay for safety to be maintained.
But I was never motivated to register until now. Why? The garbage that mdsolar keeps posting about nuclear OK, scratch that, mod me down as Flamebait for my first post I don't care.
An ad hom attack is not unexpected. As your frist post is a bit of a new low though.
There are a majority it seems on slashdot in favour of nuclear power Yet rarely have I seen a pro nuclear article on slashdot.
With that many eyes on the lookout for good news perhaps the only reason they can't find any is because there is none. This certainly isn't news about how they fixed this issue.
We manipulate and take advantage of nearby resources to improve our lives and ensure the survival of our offspring.
It's fairer to say that Nuclear power offsets the costs of improving our lives onto our offspring who are forced to deal with the waste and decommissioned reactors.
Nuclear is a viable option for electricity generation and is a part of that cycle.
Decreasingly so as a lot more of these plants reach the end of their service life, however it will certainly have a lasting impact.
I work in the nuclear industry, in the control room.
And an appeal to authority in the first post.
I'm sure you are of the highest integrity, but the industry you work in has made a habit of lying and being untrustworthy. Paid and unpaid shills are plentiful and anyone else is treated with the disdain you have demonstrated.
I have read many of mdsolars posts and have only seen him *being* trolled
A clueless fanboy's definition of a troll is any mention of their pet topic that contains something other than high praise.
I wish they would actually learn abut their pet topics and become fanboys with a clue instead, it would cut down on the meaningless noise.
So true, most argue without facts and have nothing much to offer.
As soon as I saw the word "nuclear" in the subject, I knew who the submitter was.
And I knew that anyone expressing doubt about the value of nuclear power would be attacked.
For those new around here, mdsolar is Slashdot's long-time anti-unclear troll, so I'm posting this as a forewarning to you.
For those new around here you'll find that the articles mdsolar post are accurate and good sources of information from actual scientists and engineers.
Unclear power - thats an interesting characterization of Nuclear power you have made Prune.
His posting history shows he regularly contributes anti-nuclear articles,
Pro-and anti Unclear power is a matter of perspective. For those new around here a lot of/.rs have an idealized version of nuclear power that they transmute onto reality typically with no basis in actual fact and rarely supported by evidence that they will provide. I suspect that much of this attitude comes from wanting to maintain a beleif system that nuclear power is safe.
and when he gets told, he typically resorts to personal attacks on those he disagrees with.
For those new around here,
this is the kind of attack you can expect for trying to have a rational discussion and uncover the actual facts about nuclear power. Wrt nuclear power social proof and groupthink about nuclear power expressed here will almost certainly mean you will be modded down. The personal attacks you will be subject to illustrate the mentality of the pro-nuclear camp who view any presentation of *any* facts about nuclear power as "anti" nuclear.
I have read many of mdsolars posts and have only seen him *being* trolled. It looks like you are doing the thing you accuse others of Prune, can you link to an actual post of mdsolar's where such trolling has occurred?
If you're not interested in going down this path, the best option is just to ignore him. As they say: don't feed the trolls. Now if we could only get the powers-that-be here to ignore his submissions...
This is the essence of conversations about nuclear power at slashdot. Here we see an article about Engineers protesting against a Basis Design Issue that they have uncovered. They are petitioning the NRC to issue safety directives to avert the real potential of a cooling failure leading to a nuclear accident. The reaction to this call to improve safety and resolve the design issue is to call the OP, and the article, a troll.
Groupthink is nuclear power's greatest asset and liability.
So the underlying problem is there is phenomenological evidence that indicates that for long stretches of time, some cartel can controls 51% of the block chain compute and is withholding submits so it can privately mine them before distributing them.
You have to have the most up to date ASIC all of the time or you are at a disadvantage. And electricity. It's a logical conclusion that if someone can control the volume of hardware and electricity thrown at it then they can dominate.
Maybe the first flaw to be overcome with digital currency is for it to cope with it's own implementation issues.
If I understand bitcoin correctly, both of those are its fundamental achilles heel, assumed never to happen, and therefore the currency is now subject to manipulation, and thus eventually worthless.
Wasn't it widley publicized *how* you could manipulate it?
Perhaps if it can always be manipulated, it is worthless. If you a bitcoin that is worthless you still have a bitcoin. It doesn't have a *value* less than zero, like some other investments might have, so rather than being "worthless" it's "worth nothing" for some period of time until someone says it is "worth something".
Currency was spent to provide that electricity to create (mine) a bitcoin, which also had value assigned to it.
Dams are clean energy producers and have to be way safer than that evil nuclear stuff. The estimates must be off by a few orders of magnitude. Nothing else makes sense.
Perhaps it means the things we engineer can fail and that when they do they have consequences.
If you are all familiar with the current "War on sanity" you will all recognise that encryption is the next thing that is being targetted by power. You've seen Apple vs FBI and the rest of the bullshit attacks on encryption, well here comes the law.
I read DTCA when it was proposed and what concerned me most was it allows government to take control of your inventions and patents whilst turning encryption into a controlled munition. Therefore if you show someone how to use encryption you are an arms dealer in the eyes of the law.
It's a sloppy way to close all doors on using encryption in Australia, invented by the hamfisted Abbot government that Australia deserved. I would not be surprised to see a similar attempt in the US/Canada and UK through other legal avenues.
The theme park looks great but the people who own it are true psychopaths. This is one of the things that make our society inane, things that are important like people and laws that make society are ignored while disney theme parks are celebrated like a sugar drink that tastes great at the time, but ultimately leaves you empty and unsatisfied when the rush subsides.
It must be horrible for the families the former Disney IT people who have to explain to their kids why they won't be going whilst lines of people go not knowing that the assholes who dull their frustration for a little while, also cause it . Disney sure knows how to be evil and I contributed too, I watched Star Wars and I am guilty of enjoying it. That makes me a hypocrite, so no thanks Disney, I won't be visiting your theme park. What a shame they don't practice the values they espouse in their movies.
Meanwhile, in the real world, Disney has also helped construct the new TPP ride for our enjoyment. We all wait in the line in antici----pation, we can't change our mind, we don't know what the ride will be like and we can't get off.
I take it that you work for Microsoft then?
Ready for that corner office?
I would give up my corner office so that we could install more windows servers, they are that good. You don't strike me as stupid, have you heard of Windows? Have you used it? It is wonderful and has so many great features! You should try Windows 10 Today!!!
It's ok for them to ship our jobs there. But it's not ok for us to ship the products made here. Care to explain that?
Yes, they are already poor, starving and begging for *any* job. They are unlikely to agitate for political change and no one should enjoy freedom unless they are obscenely wealthy.
But if your company wants you to vote a certain way, they can "suggest" it, and in at will https://en.wikipedia.org/wiki/... they can fire you for not voting they way they "suggest"
When I worked for NCR, HR would go around with paycheck deduction forms to contribute to the United Way - in the name of NCR.
Disney does exactly the same thing with the United Way. It was usually the union shop stewards at Disney World that went around trying to guilt everyone into donating. I wouldn't even accept the forms. Sure, you get the stinkeye for it, but I really didn't care.
Thanks for the warning, personally never encountered the practise. It occurred to me from reading your comments that if I ever did, I would take the form and donate 10 cents. Then it would be their issue because only a hypocrite would take issue with how much you donate.
Windows 10 is the best windows offering Microsoft has ever come up with, it's truly a fantastic O.S. Windows 10 beta testers should happy that Microsoft asks them so many questions, because it just shows how much microsoft values their beta testers time. I would go as far as saying that Windows 10 beta testers should pay microsoft twice the rrp because they are getting to see all the great new features of 10 *first*, who else get's such a privilege? Cetainly not "linux' beta testers, if they even have them.
With the release of windows 10 more and more people will be flocking to the Windows platform - it's that good.
If jackthreads can't afford to pay the market rates for someone who puts together the infrastructure that *runs their business* then perhaps they can't afford to be in business.
Perhaps Jack-ass-threads (sorry: I *had* to get it out of my system) O'neil should be lobbying congress to reduce the financial debt someone gets to be able to accumulate the education required. Then *more* people capable of doing what they want will be available and the market rate will change.
Instead they all continually argue to erode the pool of skilled people who can do those things. Their short term thinking expects someone else to be on the paying end of capitalism which becomes their argument for more of these visa. I think that's called pissing into the fountain you are drinking from.
This would be an appropriate scenario for an IT Union looking after Professional IT worker's interests by lobbying at a political level about how appropriate H1B visas are in the community. It's the 21st century folks, it doesn't have to be about picket lines and strikes, it could be about an IT Union arguing which legal constructs are acceptable in the community and, which are not to a Senator. Who else do you expect to do it, because you certainly have an example of the type of people having these discussions *against* IT people's interests.
The issue is that there is a leak of something that isn't supposed to leak, and they can't seem to fix it. If it isn't fixed it will eventually become dangerous. It doesn't inspire much confidence in their ability to run their plant safely either.
Davis Besse was another reactor with "unexplained' issues during operation. As it turns out a leak was spraying borated water onto the underside of the reactor head and corroded a football size hole into it. It bore most of the way through six inches of steel with less than an inch remaining.
Any unexplained behaviour of a Nuclear reactor's cooling systems introduces the risk of a Loss Of Cooling Accident and that is the point here. At Davis Besse increased frequency of water filter changes should have alerted management to the need for an investigation and it was ignored. That led to criminal charges at that plant.
An unexplained leak, increasing in volume, from a Nuclear Reactor that is within 50 miles of a city with 25 million people in it is a threat that should be dealt with. Indian Point has a history of issues and less than a year ago a fire at the plant led to flooding in a swtichgear room that controlled power for emergency systems. Leaking valves, corroded parts and something as simple as blocked drains at the plant reduced the plants ability to deal with emergency situations.
This is important because it tells us that the operator does not take plant safety seriously and consequently the NRC found that I.P operators had repeatedly breached federal regulations. If the operators of Indian Point are too cheap to install a $200,000 alarm system to alert controllers of a problem with their emergency systems I have little confidence in them tracking down issues like this.
Fukushima showed us what can happen when the operators of plants do not deal with safety issues. People may not be concerned with what is leaking, but they should be concerned that no one knows where this water is leaking *from* because these are the types of things that lead to accidents.
Wow! Most useful and on topic post under this submission. I will be converting this into and adding it to my personal documentation. Thanks a bunch!
No problem, it was a good opportunity to articulate what I have been doing to people who could actually understand it, so I'm glad you asked.
My friends (bandmates?) just left. One of the cool things I've found I can do is get them more involved in the production process as well, which is what we did tonight.
Basically they come around (usually with beer and weed) and I take them through a bunch of effects or some elements that I prepared earlier for the songs. Then we go through using Ardour together and I ask them what they hear, anything, and act as a conduit to the application. When you get your own ego out of their way, their creative juices start flowing and suddenly there are three brains coming up with ideas with one brain (yours) in the logical space applying them.
This involves everyone in the sound (so they own it) and reduces my workload so I can apply my creativity into meshing the ideas together later on. Another cool thing is, we have a great time and everyone goes home laughing so it becomes an incredibly unique social activity.
Even though it's hard work, there is no reason you can't have a great time with it if you are careful with preparation and get the logical and structural elements out of the way first so that your friends, the musicians, can come up with good ideas. I hope you have a great time with it too.
Executing in sequence and running in parallel are two different thing. The processes are spawned as background tasks. Init does not wait for them to complete before spawning the next. That is how init works and any code trying to do the same thing will use a similar method to do it. Parallelism is driven by process allocation to a core by the kernel after the process is spawned. init does not wait for them to complete before starting the next one.
SysV init replacements are a superset of init's features, so the use cases are broadly the same, however the environment has changed quite a bit:
It would be truer to say the perception has changed.
hotplugging of various devices is far more common, changing networks, and so on. We're also seeing a rise in containerized applications and virtualization. Computer systems are becoming very complex, so we must decide where that complexity should be located.
Complexity is relative. They are no more or less complex than they ever have been. All you are speaking of is context.
The obvious choice for this type of task is to abstract the common functionality into a shared library. There is not really any way to do that and keep init small: the complexity must exist somewhere,
This is an argument to justify the existence of systemd, not one that is a design limitation of init. i.e. you haven't considered *how* to achieve this in init by breaking down the complexity.
and it makes no sense to have init exist simply to kick off the "real" service manager.
Why? Do you propose changing from systemd to something else when the use cases change again? Seems completely appropriate for init to start a service manager (or a runlevel manager) that can compartmentalise different type of services appropriate to the context of the system.
So the question is not really "what use cases are there?", but "what should init do?",
Exactly what it does. All of the functionality you speak of should be handled by something else. If an input controller from a touch screen fails, it doesn't mean init should manage input controller functionality.
and again, the consensus for the last couple decades is to move functionality from scripts to the service manager, instead of relying on each and every script to do things correctly.
No argument from me that rc scripts are used incorrectly - you are arguing about how inits *support* functionality is used incorrectly.
The most basic task seems to be dependency resolution: it's simpler to add markup to a script that tells the manager what it needs than to write dozens of lines of code trying to figure out if ServiceA and InterfaceB are up.
So instead you are talking about writing thousands of line of code to do that. You are saying that the kernel should start a service manager instead of a process manager.
I don't disagree about the issue, I disagree with the proposed solution. What you are arguing is that because people didn't use init properly in the first place which accumulated all of this technical debt, the proposal is to solve that by introducing even more technical debt.
I'd be in favour of a campaign to reduce that technical debt because it will make for efficient fast systems.
Starting services in parallel is another obvious improvement. Socket activation is also beneficial.
The article you link to shows a misunderstanding of how init works. It only talks about rc script functionality of init - not init functionality. Everything that systemd subjectively shows started in parallel can be started in parallel by init as well.
"Lexicon Alpha 2-channel interface is a $49 POS USB"
Yes, it is a super cheapy and I am fully aware of it's limitations.
I use 2 delta 1010lts, clock synced with sp/diff. I pay attention to the impedence and quality of the cable used for timing signals. No cheap cables. I've had these for a while. I gang them together using alsa into a single 16 channel input.
In your case, HW on a budget, make sure to have good clean power supplies. Consider using a small motor cycle battery to power your device so you can imnprove the input quality of your signal source. Use good cables, make sure you dedicate a USB interface to it. Pay attention to where mains voltage is.
Standard kernel and misc. other was no good. Adopted a low latency kernel (has it's own dangers) and made other system mods and no more bullshit.
Use the real time patches as well, pay attention to configuring io schedulers and picking good underlying filesystem (I like Jfs on ssd right now). It pays money to know about filesystem performance. Linux, hands down, kicks the shit out of MAC and widows for filesystem and CPU performance on the same hardware, short of MAC guys actually knowing how to utilize the underlying power of the BSD OS that makes Macintoshes what they are. The only thing faster than a Linux kernel is a Solaris kernel. If I used a MAC, I would do exactly what I would do in linux and compile Ardour and Jack on a MAC to see what it can do. This is the foundation for what you produce music on - that is why it is important to understand it.
You have to have the mindset to actually do innovative stuff because it's actually, mentally hard work. Those in a hurry to get into their creative space and unable to delay gratification to understand the underlying structural concepts that makes their equipment actually be a recording system deny themselves the opportunity to do something outstandingly different. I have Logic, I use Ardour because once you understand the flexibility you get to mangle the workflow you don't want to use pro-tools to produce the same sounds everyone else makes. So DAWs in the Linux space force you to choose between mainstream or innovation. Unforgiving, but extremely rewarding.
After finding it actually worked, I came here hoping for advice and what to buy and not to buy if I decided to spring for more.
Fuckin A, it's totally worth it. My upgrades to my studio will be PCie RME cards maybe 32 channels, a Mackie control surface.
In terms of Mics I have Rode: 2 beautiful pencil, 1 valve NTK, 1 NT1. AKG: some fat diaphram kick mic (that I use for bass amp), a AKG vocal. Shure SM57/58 (a few of them), Senheiser E600, 80 - shit I got a lot more now I think about it, I scored this old, very rare Zephr 18 x A Grid. Buy good desks, pay attention to how many busses you can squeeze out of a desk. Have a look around for some old tape four tracks, which actually make for pretty good 8 channel pre-amps for your computer, that way you also get off board eqs and pre-amps. Also look for a good quality desk, quality power supplies. I bought a Yamaha emx 600 over a decade ago and it was worth every cent, most good desks will have those features.
This is my first venture into home recording using Linux and all documentation out there on the subject is sketchy at best... home as in outside the needs of a full blown studio.
Don't look back, jump in. Don't listen to the naysayers. There are challenges, but they are worth it for the skills you acquire, which is also hard work. I used to use CCRMA, fedora, cut down kernels however now, I use ubuntu studio or linux mint with the low latency and rt kernel - available from the repos and apt. Pretty straight forward. You don't have to go as far as I went, however I am a little embarrasingly obsessed with sound and performance computing.
What these Mac guys *can't* do is yeild a stripped down thoughrobred OS that supports
Slashdot Mirror
The reality would be...
bumping some orbital body large enough to obliterate the area in question and small enough not to destroy the planet's surface. You would classify it enough so that some of your own people would die so that you could bond with the natives in a shared experience of grief, tell them that the area is dangerous and that by stretching our own meager resources we might have the equipment to render the area safe again, one day. In the meantime we can only protect you natives if you stay away from the area.
Why the fuck would you risk your own assets when you can control what falls on where from orbit and no one can see your preparations and planning. In that regard Avatar is more stupid than a bunch of Jar Jar Binks.
That was a perfect /. submission. An AI that could pass the Turning Test by being indistinguishable from a jingoistic blabber mouth.
Oh, is that where all the AC nukie shills come from.
You are nothing like the airline industry who actually is a learning industry. You've learned how to PR spin and do the absolute minimum you have to do. You do the same arrogant dismissal of people's concerns and treat them like they are stupid. Fukushima proved the Nuclear Industry learned nothing from Chernobyl except how to better cover evidence and ensure the flow of information is stifled.
I used to support nuclear power, I thought it would save the world and the more I learned and asked questions the more I got labelled as "anti" unclear power.
Indeed it is this very conceit that you demonstrate that is cited in the Official report on the Fukushima accident as a key reason why Japan's unclear industry "managed to avoid absorbing the critical lessons learned from Three Mile Island and Chernobyl" and "how it became accepted practice to resist regulatory pressure and cover up small-scale accidents" like we see here.
The last thing it says about this conceited attitude is: "It was this mindset that led to the disaster at the Fukushima Daiichi Nuclear Plant. "
The attitude you display, as a professional, is no different and is a clear demonstration that the only thing you've learned from Fukushima is to point fingers and say "Not our problem".
The vulnerabilities at the Fukushima reactors were well know for decades before and GE issued procedures for ensuring that those situations would not arise for that generation reactor. The operators did not take sufficient measures to protect the reactor or the community around it.
Everything that happened in that accident was predicted by the American Society of Mechanical Engineers from an un- fuelled pressure test of that generation reactor because it was those results that led GE to devise those condition to mitigate the basis design issues that they uncovered. Those factors were not taken seriously enough by TEPCO and that is what led to the accident.
When Nuclear power fails you people claim that no one dies whilst it obliterates communities. Fukushima province was destroyed by a Tsunami however the reason it's people can't return *home* and rebuild is because a nuclear reactor spewed radioactive isotopes all over the place where that community used to exist. The same thing happened at Chernobyl.
But you guys can never take responsibility for anything, minimize everything, attack anyone who has their own concerns no matter how valid and no one has any choice but to accept that unclear power is there.
They may work well. What we have learned is that human organizational systems are not mature enough to handle nuclear power safely. Commercial reactors that are operated by for profit operators have demonstrated an unwillingness to pay for safety to be maintained.
Excuse me drinkypoo, that reply was to monkeyman.kix
An ad hom attack is not unexpected. As your frist post is a bit of a new low though.
With that many eyes on the lookout for good news perhaps the only reason they can't find any is because there is none. This certainly isn't news about how they fixed this issue.
It's fairer to say that Nuclear power offsets the costs of improving our lives onto our offspring who are forced to deal with the waste and decommissioned reactors.
Decreasingly so as a lot more of these plants reach the end of their service life, however it will certainly have a lasting impact.
And an appeal to authority in the first post. I'm sure you are of the highest integrity, but the industry you work in has made a habit of lying and being untrustworthy. Paid and unpaid shills are plentiful and anyone else is treated with the disdain you have demonstrated.
A clueless fanboy's definition of a troll is any mention of their pet topic that contains something other than high praise. I wish they would actually learn abut their pet topics and become fanboys with a clue instead, it would cut down on the meaningless noise.
So true, most argue without facts and have nothing much to offer.
And I knew that anyone expressing doubt about the value of nuclear power would be attacked.
For those new around here you'll find that the articles mdsolar post are accurate and good sources of information from actual scientists and engineers.
Unclear power - thats an interesting characterization of Nuclear power you have made Prune.
Pro-and anti Unclear power is a matter of perspective. For those new around here a lot of /.rs have an idealized version of nuclear power that they transmute onto reality typically with no basis in actual fact and rarely supported by evidence that they will provide. I suspect that much of this attitude comes from wanting to maintain a beleif system that nuclear power is safe.
For those new around here, this is the kind of attack you can expect for trying to have a rational discussion and uncover the actual facts about nuclear power. Wrt nuclear power social proof and groupthink about nuclear power expressed here will almost certainly mean you will be modded down. The personal attacks you will be subject to illustrate the mentality of the pro-nuclear camp who view any presentation of *any* facts about nuclear power as "anti" nuclear.
I have read many of mdsolars posts and have only seen him *being* trolled. It looks like you are doing the thing you accuse others of Prune, can you link to an actual post of mdsolar's where such trolling has occurred?
This is the essence of conversations about nuclear power at slashdot. Here we see an article about Engineers protesting against a Basis Design Issue that they have uncovered. They are petitioning the NRC to issue safety directives to avert the real potential of a cooling failure leading to a nuclear accident. The reaction to this call to improve safety and resolve the design issue is to call the OP, and the article, a troll.
Groupthink is nuclear power's greatest asset and liability.
It left some heavy shit!
So the underlying problem is there is phenomenological evidence that indicates that for long stretches of time, some cartel can controls 51% of the block chain compute and is withholding submits so it can privately mine them before distributing them.
You have to have the most up to date ASIC all of the time or you are at a disadvantage. And electricity. It's a logical conclusion that if someone can control the volume of hardware and electricity thrown at it then they can dominate.
Maybe the first flaw to be overcome with digital currency is for it to cope with it's own implementation issues.
If I understand bitcoin correctly, both of those are its fundamental achilles heel, assumed never to happen, and therefore the currency is now subject to manipulation, and thus eventually worthless.
Wasn't it widley publicized *how* you could manipulate it?
Perhaps if it can always be manipulated, it is worthless. If you a bitcoin that is worthless you still have a bitcoin. It doesn't have a *value* less than zero, like some other investments might have, so rather than being "worthless" it's "worth nothing" for some period of time until someone says it is "worth something".
Currency was spent to provide that electricity to create (mine) a bitcoin, which also had value assigned to it.
Or am I wrong?
It could be a matter of timing.
Dams are clean energy producers and have to be way safer than that evil nuclear stuff. The estimates must be off by a few orders of magnitude. Nothing else makes sense.
Perhaps it means the things we engineer can fail and that when they do they have consequences.
If you are all familiar with the current "War on sanity" you will all recognise that encryption is the next thing that is being targetted by power. You've seen Apple vs FBI and the rest of the bullshit attacks on encryption, well here comes the law.
I read DTCA when it was proposed and what concerned me most was it allows government to take control of your inventions and patents whilst turning encryption into a controlled munition. Therefore if you show someone how to use encryption you are an arms dealer in the eyes of the law.
It's a sloppy way to close all doors on using encryption in Australia, invented by the hamfisted Abbot government that Australia deserved. I would not be surprised to see a similar attempt in the US/Canada and UK through other legal avenues.
The theme park looks great but the people who own it are true psychopaths. This is one of the things that make our society inane, things that are important like people and laws that make society are ignored while disney theme parks are celebrated like a sugar drink that tastes great at the time, but ultimately leaves you empty and unsatisfied when the rush subsides.
It must be horrible for the families the former Disney IT people who have to explain to their kids why they won't be going whilst lines of people go not knowing that the assholes who dull their frustration for a little while, also cause it . Disney sure knows how to be evil and I contributed too, I watched Star Wars and I am guilty of enjoying it. That makes me a hypocrite, so no thanks Disney, I won't be visiting your theme park. What a shame they don't practice the values they espouse in their movies.
Meanwhile, in the real world, Disney has also helped construct the new TPP ride for our enjoyment. We all wait in the line in antici----pation, we can't change our mind, we don't know what the ride will be like and we can't get off.
Whooosssssshhhhh
I take it that you work for Microsoft then? Ready for that corner office?
I would give up my corner office so that we could install more windows servers, they are that good. You don't strike me as stupid, have you heard of Windows? Have you used it? It is wonderful and has so many great features! You should try Windows 10 Today!!!
Nope. Does not. It's Oger.
Hmmm, Bob Oger - a good name for a troll!
It's ok for them to ship our jobs there. But it's not ok for us to ship the products made here. Care to explain that?
Yes, they are already poor, starving and begging for *any* job. They are unlikely to agitate for political change and no one should enjoy freedom unless they are obscenely wealthy.
Here is my ideal IP solution.
Unfortunately you have the TPP instead and I don't think they are taking suggestions.
But if your company wants you to vote a certain way, they can "suggest" it, and in at will https://en.wikipedia.org/wiki/... they can fire you for not voting they way they "suggest"
At least you will know how *not* to vote.
When I worked for NCR, HR would go around with paycheck deduction forms to contribute to the United Way - in the name of NCR. Disney does exactly the same thing with the United Way. It was usually the union shop stewards at Disney World that went around trying to guilt everyone into donating. I wouldn't even accept the forms. Sure, you get the stinkeye for it, but I really didn't care.
Thanks for the warning, personally never encountered the practise. It occurred to me from reading your comments that if I ever did, I would take the form and donate 10 cents. Then it would be their issue because only a hypocrite would take issue with how much you donate.
Windows 10 is the best windows offering Microsoft has ever come up with, it's truly a fantastic O.S. Windows 10 beta testers should happy that Microsoft asks them so many questions, because it just shows how much microsoft values their beta testers time. I would go as far as saying that Windows 10 beta testers should pay microsoft twice the rrp because they are getting to see all the great new features of 10 *first*, who else get's such a privilege? Cetainly not "linux' beta testers, if they even have them.
With the release of windows 10 more and more people will be flocking to the Windows platform - it's that good.
If jackthreads can't afford to pay the market rates for someone who puts together the infrastructure that *runs their business* then perhaps they can't afford to be in business.
Perhaps Jack-ass-threads (sorry: I *had* to get it out of my system) O'neil should be lobbying congress to reduce the financial debt someone gets to be able to accumulate the education required. Then *more* people capable of doing what they want will be available and the market rate will change.
Instead they all continually argue to erode the pool of skilled people who can do those things. Their short term thinking expects someone else to be on the paying end of capitalism which becomes their argument for more of these visa. I think that's called pissing into the fountain you are drinking from.
This would be an appropriate scenario for an IT Union looking after Professional IT worker's interests by lobbying at a political level about how appropriate H1B visas are in the community. It's the 21st century folks, it doesn't have to be about picket lines and strikes, it could be about an IT Union arguing which legal constructs are acceptable in the community and, which are not to a Senator. Who else do you expect to do it, because you certainly have an example of the type of people having these discussions *against* IT people's interests.
The issue is that there is a leak of something that isn't supposed to leak, and they can't seem to fix it. If it isn't fixed it will eventually become dangerous. It doesn't inspire much confidence in their ability to run their plant safely either.
Davis Besse was another reactor with "unexplained' issues during operation. As it turns out a leak was spraying borated water onto the underside of the reactor head and corroded a football size hole into it. It bore most of the way through six inches of steel with less than an inch remaining.
Any unexplained behaviour of a Nuclear reactor's cooling systems introduces the risk of a Loss Of Cooling Accident and that is the point here. At Davis Besse increased frequency of water filter changes should have alerted management to the need for an investigation and it was ignored. That led to criminal charges at that plant.
An unexplained leak, increasing in volume, from a Nuclear Reactor that is within 50 miles of a city with 25 million people in it is a threat that should be dealt with. Indian Point has a history of issues and less than a year ago a fire at the plant led to flooding in a swtichgear room that controlled power for emergency systems. Leaking valves, corroded parts and something as simple as blocked drains at the plant reduced the plants ability to deal with emergency situations.
This is important because it tells us that the operator does not take plant safety seriously and consequently the NRC found that I.P operators had repeatedly breached federal regulations. If the operators of Indian Point are too cheap to install a $200,000 alarm system to alert controllers of a problem with their emergency systems I have little confidence in them tracking down issues like this.
Fukushima showed us what can happen when the operators of plants do not deal with safety issues. People may not be concerned with what is leaking, but they should be concerned that no one knows where this water is leaking *from* because these are the types of things that lead to accidents.
Wow! Most useful and on topic post under this submission. I will be converting this into and adding it to my personal documentation. Thanks a bunch!
No problem, it was a good opportunity to articulate what I have been doing to people who could actually understand it, so I'm glad you asked.
My friends (bandmates?) just left. One of the cool things I've found I can do is get them more involved in the production process as well, which is what we did tonight.
Basically they come around (usually with beer and weed) and I take them through a bunch of effects or some elements that I prepared earlier for the songs. Then we go through using Ardour together and I ask them what they hear, anything, and act as a conduit to the application. When you get your own ego out of their way, their creative juices start flowing and suddenly there are three brains coming up with ideas with one brain (yours) in the logical space applying them.
This involves everyone in the sound (so they own it) and reduces my workload so I can apply my creativity into meshing the ideas together later on. Another cool thing is, we have a great time and everyone goes home laughing so it becomes an incredibly unique social activity.
Even though it's hard work, there is no reason you can't have a great time with it if you are careful with preparation and get the logical and structural elements out of the way first so that your friends, the musicians, can come up with good ideas. I hope you have a great time with it too.
All the best.
This is sequential and not parallel.
Executing in sequence and running in parallel are two different thing. The processes are spawned as background tasks. Init does not wait for them to complete before spawning the next. That is how init works and any code trying to do the same thing will use a similar method to do it. Parallelism is driven by process allocation to a core by the kernel after the process is spawned. init does not wait for them to complete before starting the next one.
SysV init replacements are a superset of init's features, so the use cases are broadly the same, however the environment has changed quite a bit:
It would be truer to say the perception has changed.
hotplugging of various devices is far more common, changing networks, and so on. We're also seeing a rise in containerized applications and virtualization. Computer systems are becoming very complex, so we must decide where that complexity should be located.
Complexity is relative. They are no more or less complex than they ever have been. All you are speaking of is context.
The obvious choice for this type of task is to abstract the common functionality into a shared library. There is not really any way to do that and keep init small: the complexity must exist somewhere,
This is an argument to justify the existence of systemd, not one that is a design limitation of init. i.e. you haven't considered *how* to achieve this in init by breaking down the complexity.
and it makes no sense to have init exist simply to kick off the "real" service manager.
Why? Do you propose changing from systemd to something else when the use cases change again? Seems completely appropriate for init to start a service manager (or a runlevel manager) that can compartmentalise different type of services appropriate to the context of the system.
So the question is not really "what use cases are there?", but "what should init do?",
Exactly what it does. All of the functionality you speak of should be handled by something else. If an input controller from a touch screen fails, it doesn't mean init should manage input controller functionality.
and again, the consensus for the last couple decades is to move functionality from scripts to the service manager, instead of relying on each and every script to do things correctly.
No argument from me that rc scripts are used incorrectly - you are arguing about how inits *support* functionality is used incorrectly.
The most basic task seems to be dependency resolution: it's simpler to add markup to a script that tells the manager what it needs than to write dozens of lines of code trying to figure out if ServiceA and InterfaceB are up.
So instead you are talking about writing thousands of line of code to do that. You are saying that the kernel should start a service manager instead of a process manager.
I don't disagree about the issue, I disagree with the proposed solution. What you are arguing is that because people didn't use init properly in the first place which accumulated all of this technical debt, the proposal is to solve that by introducing even more technical debt.
I'd be in favour of a campaign to reduce that technical debt because it will make for efficient fast systems.
Starting services in parallel is another obvious improvement. Socket activation is also beneficial.
The article you link to shows a misunderstanding of how init works. It only talks about rc script functionality of init - not init functionality. Everything that systemd subjectively shows started in parallel can be started in parallel by init as well.
Init/inittab was intentionally simple. I
"Lexicon Alpha 2-channel interface is a $49 POS USB"
Yes, it is a super cheapy and I am fully aware of it's limitations.
I use 2 delta 1010lts, clock synced with sp/diff. I pay attention to the impedence and quality of the cable used for timing signals. No cheap cables. I've had these for a while. I gang them together using alsa into a single 16 channel input. In your case, HW on a budget, make sure to have good clean power supplies. Consider using a small motor cycle battery to power your device so you can imnprove the input quality of your signal source. Use good cables, make sure you dedicate a USB interface to it. Pay attention to where mains voltage is.
Standard kernel and misc. other was no good. Adopted a low latency kernel (has it's own dangers) and made other system mods and no more bullshit.
Use the real time patches as well, pay attention to configuring io schedulers and picking good underlying filesystem (I like Jfs on ssd right now). It pays money to know about filesystem performance. Linux, hands down, kicks the shit out of MAC and widows for filesystem and CPU performance on the same hardware, short of MAC guys actually knowing how to utilize the underlying power of the BSD OS that makes Macintoshes what they are. The only thing faster than a Linux kernel is a Solaris kernel. If I used a MAC, I would do exactly what I would do in linux and compile Ardour and Jack on a MAC to see what it can do. This is the foundation for what you produce music on - that is why it is important to understand it.
You have to have the mindset to actually do innovative stuff because it's actually, mentally hard work. Those in a hurry to get into their creative space and unable to delay gratification to understand the underlying structural concepts that makes their equipment actually be a recording system deny themselves the opportunity to do something outstandingly different. I have Logic, I use Ardour because once you understand the flexibility you get to mangle the workflow you don't want to use pro-tools to produce the same sounds everyone else makes. So DAWs in the Linux space force you to choose between mainstream or innovation. Unforgiving, but extremely rewarding.
After finding it actually worked, I came here hoping for advice and what to buy and not to buy if I decided to spring for more.
Fuckin A, it's totally worth it. My upgrades to my studio will be PCie RME cards maybe 32 channels, a Mackie control surface.
In terms of Mics I have Rode: 2 beautiful pencil, 1 valve NTK, 1 NT1. AKG: some fat diaphram kick mic (that I use for bass amp), a AKG vocal. Shure SM57/58 (a few of them), Senheiser E600, 80 - shit I got a lot more now I think about it, I scored this old, very rare Zephr 18 x A Grid. Buy good desks, pay attention to how many busses you can squeeze out of a desk. Have a look around for some old tape four tracks, which actually make for pretty good 8 channel pre-amps for your computer, that way you also get off board eqs and pre-amps. Also look for a good quality desk, quality power supplies. I bought a Yamaha emx 600 over a decade ago and it was worth every cent, most good desks will have those features.
This is my first venture into home recording using Linux and all documentation out there on the subject is sketchy at best... home as in outside the needs of a full blown studio.
Don't look back, jump in. Don't listen to the naysayers. There are challenges, but they are worth it for the skills you acquire, which is also hard work. I used to use CCRMA, fedora, cut down kernels however now, I use ubuntu studio or linux mint with the low latency and rt kernel - available from the repos and apt. Pretty straight forward. You don't have to go as far as I went, however I am a little embarrasingly obsessed with sound and performance computing.
What these Mac guys *can't* do is yeild a stripped down thoughrobred OS that supports