Remember that Everything you say will be used to burn you. Cops can lie and get away with it, and if you lie to a cop, you're fried. Do not believe anything they say, and don't try to talk your way out of it because you'll lose.
Out of interest - what makes a lawyer so special that he can talk to the cops? Are lawyers vaccinated against cop-tricks or something?
62% of the more than 18,000 U.S. consumers it polled said social media had no influence on their buying decisions.
Are the customers able to recognize whether they got influenced? I thought that current advertising methods are predominantly trying to influence subconsciousness rather then consciousness decisions.
I mean seriously, $(app vendor), your app does not need access to my location and/or phone calls in order for me to do $(menial computation X).
You mistakenly assume that "for you to do $(menial computation X)" is a reason why $(app vendor) wrote the app. It's not. He wrote it to make money. From advertising. Which can be done better if he can "access your location and/or has access to your phone calls".
As I understand it, Metro removes abilities from the end user, while systemd actually enhances the end user by providing many more powerful features in an easy to use manner.
As an example: systemd removes the ability to run a grep on the plain text log file. And replaces it with something else. Metro also takes away the ability to do some stuff and replaces it with something that the marketing department claims to be just as capable or even more. And perhaps it's all fine when you are within the boundaries that the marketing department envisions. But Linux was never about keeping yourself within some borders. We want tweak and poke, replace X with Y and customize to no end. You can't beat flexibility of a shell script combined with textutils/binutils/fileutils.
But the main thing isn't so much that old style script init systems are inherently bad, but that they don't work well with modern day computing.
Strangely it reminds me of Metro UI on Windows that may be nice/useful on tablet/phone but was pushed by MS also to places where it does not belong: desktop or even server.
Similarly systemd may have it's uses for some specific systems and for all I care go ahead. But if systemd is going to take over my workstation and turn the boot process into something that is difficult to read/modify/log/... then I'm not going to be happy.
Bullshit. Every product has an expected lifetime. Once that passes you do not expect to get the fixes for free. If you want to get fixes for longer time you will have to pay for that. If you do not want to pay for each fix after the lifetime expires you will have to pay higher price upfront. How much are you willing to pay? For ballpark figures check how much it costs to develop software for space ships.
In some cases yes. But imagine how much it would improve if it got only 1/10th of what the state pours into proprietary solutions. And then everyone else would benefit too!
The other issue with ooBase/LibreBase is that you cannot visually design insert / update / delete queries using their QBE interface. Instead you have to write out all of the SQL.
I have about a 30% duty cycle, on a typical day.....For the most part, I try to fill my spare time with "fun" projects that just happen to marginally benefit my employer. But when something goes wrong, having me there to fix it in seconds rather than letting the company falter uselessly for days at a time more than justifies my salary.
Eh, that sounds familiar. But I have one question: do you have a report to write every week/month about what you did during that time period? Can you write there "I spent 70% of time sitting around and being ready to jump in when needed"?
I did not say that the shell scripts are portable. I just said that I can read and easily modify them on any *UX platform.
You don't need to add debug output with systemd, because you don't need to write a script to start a daemon.
You never know what someone needs. If I decide to alter iptables firewall while some VPN daemon is running, or run ftpd only when samba runs,... my reasons can be anything and obscure. And currently it is just a script away. I have some doubts whether it will be equally easy with systemd.
If a dependency issue is causing your boot to randomly fail, then your systemd configuration is horribly broken. That is exactly the problem that systemd is designed to fix. You don't know what order services are starting in because you shouldn't need to.
If systemd does badly something it is designed to fix... that does not leave a good impression;-) On a serious note: never tell me that I don't need to know how things work. If that was true I would be running Windows and people that don't know how things work would not come to me to fix things for them. "XY failed, contact the system administrator" - yeah, I'm the system administrator. So please tell me more than "cross your fingers and try to reboot". I'm the guy that knows how things work. If I can no longer be that guy I become just next useless idiot.
You can move service files to other filesystems, but then you need to tell the service config that you did this so that it can bring up that filesystem before starting the service. This is actually a lot easier to do with systemd than with sysV.
Correct me if I'm wrong, but if all filesystems are mounted early, then it does not matter where you have moved the service. How can it be easier than that?
If any other distro want's to switch to systemd I could not care less. But the danger is that the software that runs on top will become dependent on systemd. Things like KDE, bind, sshd, samba, pppd,... And that makes me worried.
Is it the case that as long as you don't have to deal with it and it works, then it's ok? What happens if you want to modify the service dependencies? Write your own deamon? Add some debug output here and there? Customize startup of some service?
All that currently requires me only to understand the bash syntax. In fact it currently requires only some familiarity with shell variables, "if" and "echo" and works from HP-UX, to FreeBSD, Slackware or Gentoo.
Slashdot Mirror
Yes, it is.
Laugh all you want. But can you provide a proof?
Out of interest - what makes a lawyer so special that he can talk to the cops? Are lawyers vaccinated against cop-tricks or something?
If phone display shows a countdown app that sets of a bomb remotely?
You think that there is a _positive_ correlation between "being married" and "having sex"?
Are the customers able to recognize whether they got influenced? I thought that current advertising methods are predominantly trying to influence subconsciousness rather then consciousness decisions.
Moses ..., is that you??
You mistakenly assume that "for you to do $(menial computation X)" is a reason why $(app vendor) wrote the app. It's not. He wrote it to make money. From advertising. Which can be done better if he can "access your location and/or has access to your phone calls".
As an example: systemd removes the ability to run a grep on the plain text log file. And replaces it with something else. Metro also takes away the ability to do some stuff and replaces it with something that the marketing department claims to be just as capable or even more. And perhaps it's all fine when you are within the boundaries that the marketing department envisions. But Linux was never about keeping yourself within some borders. We want tweak and poke, replace X with Y and customize to no end. You can't beat flexibility of a shell script combined with textutils/binutils/fileutils.
Strangely it reminds me of Metro UI on Windows that may be nice/useful on tablet/phone but was pushed by MS also to places where it does not belong: desktop or even server.
Similarly systemd may have it's uses for some specific systems and for all I care go ahead. But if systemd is going to take over my workstation and turn the boot process into something that is difficult to read/modify/log/... then I'm not going to be happy.
Minimum wage and livable wage are unrelated.
Bullshit. Every product has an expected lifetime. Once that passes you do not expect to get the fixes for free. If you want to get fixes for longer time you will have to pay for that. If you do not want to pay for each fix after the lifetime expires you will have to pay higher price upfront. How much are you willing to pay? For ballpark figures check how much it costs to develop software for space ships.
Does it mean that we can supply the enzyme to the body and cure alcoholism?
In some cases yes. But imagine how much it would improve if it got only 1/10th of what the state pours into proprietary solutions. And then everyone else would benefit too!
Steve? Is that you? Slackware still carries elvis ;-) Thank you.
And get convicted for obstructing justice. You are screwed either way.
The streaming itself is not evil. The particular implementation that prevents fair use is evil.
In order for market/democracy forces to work, the decision has to be an informed decision. It seldom is.
Also known as:
Harrisberger's Fourth Law of the Lab:
Experience is directly proportional to the amount of equipment ruined.
Oh, really?
Eh, that sounds familiar. But I have one question: do you have a report to write every week/month about what you did during that time period? Can you write there "I spent 70% of time sitting around and being ready to jump in when needed"?
You never know what someone needs. If I decide to alter iptables firewall while some VPN daemon is running, or run ftpd only when samba runs, ... my reasons can be anything and obscure. And currently it is just a script away. I have some doubts whether it will be equally easy with systemd.
If systemd does badly something it is designed to fix ... that does not leave a good impression ;-) On a serious note: never tell me that I don't need to know how things work. If that was true I would be running Windows and people that don't know how things work would not come to me to fix things for them. "XY failed, contact the system administrator" - yeah, I'm the system administrator. So please tell me more than "cross your fingers and try to reboot". I'm the guy that knows how things work. If I can no longer be that guy I become just next useless idiot.
Correct me if I'm wrong, but if all filesystems are mounted early, then it does not matter where you have moved the service. How can it be easier than that?
If any other distro want's to switch to systemd I could not care less. But the danger is that the software that runs on top will become dependent on systemd. Things like KDE, bind, sshd, samba, pppd, ... And that makes me worried.
Happy Slackware user since ~1995
Is it the case that as long as you don't have to deal with it and it works, then it's ok? What happens if you want to modify the service dependencies? Write your own deamon? Add some debug output here and there? Customize startup of some service?
All that currently requires me only to understand the bash syntax. In fact it currently requires only some familiarity with shell variables, "if" and "echo" and works from HP-UX, to FreeBSD, Slackware or Gentoo.