The relentless pressure from the government, to the point that has forced out general directors, tells us that the BBC is applying journalistic pressure where it is hurting.
Both Conservative and Labour government and parties have complained at one time or another of bias from the BBC.
Well, if everybody says that that means the BBC is hunky dory.
After a court find you liable according to the law of the land. And imprison you for breaking it.
Just try stoping any debts you have and you will be in deep doo-doo, but that does not mean that your creditor is in a dark alliance with the government.
Honestly, who cares about speed? With machines with dual and quad cores running at goodness knows how many MHz and as many GB of memory as you need this is completely irrelevant.
Can we have full W3c compliance with security in mind, please?
That is what matters frankly, all the rest is an aside.
In theory you could find all bugs in a program by simply following it step by step and then providing all the possible values for the relevant variables at each point and checking the outcomes at each point.
Good luck with that one. To give you an idea of the level of complexity you need to understand that we are dealing with numbers that scale in a similar fashion to any exponential function...
Some people keep saying this implying it is true, without any substantiation of this whatsoever.
In which way is Windows installing easier than Linux?
First of all, both things are nor remotely comparable. IN a Linux machine you have thousands of packages readily available, once the software is installed you can pretty much forget about it: no pop-ups, no reminders, no auto updates, no nonsense.
In Windows, the software will keep pestering you about all of the above, but because you say it was easier to install all of the sudden we should close your eyes and enjoy the constant pestering of all these applications.
As for RPMs and debs packages, what could be simpler than double click on them, wait for the graphic installer to pop-up and click one or two buttons at most? And if you are actually running he tool provided with modern installations you simply search for what you need, highlight it, dependencies are resolved for you, and click an install button that gets things done.
Honestly, the underestimation of the computing literacy of most people is very patronizing.
People have been conditioned to believe that ticking boxes and clicking icons is more versatile than actually telling the computer exactly what you want.
There are programs that did not foresee a situation and that can (and do) affect the infrastructure, most common are unintended denial of service attacks by programs trying to reinvent the wheel (supplanting services like email, or directory services with implementations of their own, or making unreasonable amount of requests from one of those services).
It is all great and good to believe that people will follow policies voluntarily, unfortunately experience shows this is nothing but wishful thinking, any responsible administrator *must* lock the computers while guiding users in the correct and secure way to approve new applications.
Honestly, if you go to a client that is serious about security, you will be forced to comply with their security requirements and you will be forced to stick your self employed aloofness there where the sun does not shine, fill a time sheet and gracefully thank the company that is hiring you.
Certainly some restrictions may be bad decisions, but in no serious company you will have people doing whatever they want with the computing infrastructure of the company paying their salary.
Using specific proxy server: control this via tables in a name service read at boot time and DNS pointing to the different proxy servers in your network.
Limit computers in lab to use X: use a firewall.
You can do all what you are describing but you will need to do some programming. Your scripts become the policy that governs how your network works, this is immensely more flexible and powerful than any solution constrained by what a closed source manufacturer decides to make available to you.
Sorry but I have a responsibility to keep things working, that means no development primadona will install his little application without following a procedure that ensures it is safe for the business to do so.
Employees are there to use the resources as given, and of course they can make suggestions about what would make the environment better, but the infrastructure is not theirs to do as they please, they can go home and do whatever they want on their own machines....
Group policies? What do you mean by that? All accesses to read, write or execute are handled by regular unix permissions or ACLs.
UNIX permissions are controlled by groups, group definitions are made available by means of a directory service.
Access toa given machine? Password file, or pasword table in a name service.
Single password? NIS+ or kerberos. Cached password in a laptop? Are you mad? Use a damn token that generates one time passwords.
Patch update policy? Make a repository with the latest packages to be installed, run a cron on each machine that installs these patches in a regular basis.
All of the above (and more) can be done in any Linux, Ubuntu included.
Slashdot Mirror
http://www.merriam-webster.com/dictionary/convicting
Just check the dictionary for bunnies sakes,
You can be convicted in both criminal and civil courts.
So raising the alarm is unethical?
Gee, glad to know. Death to all whistle-blowers.
An UK based hacker that broke into US's government computers is close to be extradited to the US and to face the music of the insane laws over there.
The relentless pressure from the government, to the point that has forced out general directors, tells us that the BBC is applying journalistic pressure where it is hurting.
Both Conservative and Labour government and parties have complained at one time or another of bias from the BBC.
Well, if everybody says that that means the BBC is hunky dory.
Got it?
After a court find you liable according to the law of the land. And imprison you for breaking it.
Just try stoping any debts you have and you will be in deep doo-doo, but that does not mean that your creditor is in a dark alliance with the government.
Honestly, who cares about speed? With machines with dual and quad cores running at goodness knows how many MHz and as many GB of memory as you need this is completely irrelevant.
Can we have full W3c compliance with security in mind, please?
That is what matters frankly, all the rest is an aside.
At least in the UK in certain accounts.
In the real world you actually sit and think about how you are going to throw 35000 away...
They should.
Anybody selling mangoes, apples or oranges knows that if the damn things are not selling you have to cut the price.
To be musing about this like if discovering something ultra insightful is frankly pathetic...
In theory you could find all bugs in a program by simply following it step by step and then providing all the possible values for the relevant variables at each point and checking the outcomes at each point.
Good luck with that one. To give you an idea of the level of complexity you need to understand that we are dealing with numbers that scale in a similar fashion to any exponential function...
It scares me shitless to think about a cat that can annoy me either dead or alive.
Your reply is a perfect example of why we need more of them.
Only they know all the reticence and outright discrimination suffered by women in the workplace, sometimes disguised as "curiosity" funnily enough.
That any developer over 38 or thereabouts would have not heard about this while in University then (I know I didn't).
It is like demanding that all physicists become conversant with relativity theory in the 1920s...
If you search for "AAC" in synaptic you get both the name of the package and the description of what the package does.
And often now if you click in a common file type Ubuntu asks you if you want to install codecs, plugins or whatever you need.
Some people keep saying this implying it is true, without any substantiation of this whatsoever.
In which way is Windows installing easier than Linux?
First of all, both things are nor remotely comparable. IN a Linux machine you have thousands of packages readily available, once the software is installed you can pretty much forget about it: no pop-ups, no reminders, no auto updates, no nonsense.
In Windows, the software will keep pestering you about all of the above, but because you say it was easier to install all of the sudden we should close your eyes and enjoy the constant pestering of all these applications.
As for RPMs and debs packages, what could be simpler than double click on them, wait for the graphic installer to pop-up and click one or two buttons at most? And if you are actually running he tool provided with modern installations you simply search for what you need, highlight it, dependencies are resolved for you, and click an install button that gets things done.
Honestly, the underestimation of the computing literacy of most people is very patronizing.
People have been conditioned to believe that ticking boxes and clicking icons is more versatile than actually telling the computer exactly what you want.
There are programs that did not foresee a situation and that can (and do) affect the infrastructure, most common are unintended denial of service attacks by programs trying to reinvent the wheel (supplanting services like email, or directory services with implementations of their own, or making unreasonable amount of requests from one of those services).
It is all great and good to believe that people will follow policies voluntarily, unfortunately experience shows this is nothing but wishful thinking, any responsible administrator *must* lock the computers while guiding users in the correct and secure way to approve new applications.
Honestly, if you go to a client that is serious about security, you will be forced to comply with their security requirements and you will be forced to stick your self employed aloofness there where the sun does not shine, fill a time sheet and gracefully thank the company that is hiring you.
But the poster is so vague that he is not going to get a good answer.
What exactly does he mean with "locking down" a machine for example?
Many restrictions are there for a reason.
Certainly some restrictions may be bad decisions, but in no serious company you will have people doing whatever they want with the computing infrastructure of the company paying their salary.
Using specific proxy server: control this via tables in a name service read at boot time and DNS pointing to the different proxy servers in your network.
Limit computers in lab to use X: use a firewall.
You can do all what you are describing but you will need to do some programming. Your scripts become the policy that governs how your network works, this is immensely more flexible and powerful than any solution constrained by what a closed source manufacturer decides to make available to you.
The company or the employees?
Sorry but I have a responsibility to keep things working, that means no development primadona will install his little application without following a procedure that ensures it is safe for the business to do so.
Employees are there to use the resources as given, and of course they can make suggestions about what would make the environment better, but the infrastructure is not theirs to do as they please, they can go home and do whatever they want on their own machines ....
How do you want to do it? Using telepathy?
ssh *is* the way to do it, this can easily be automated with some basic scripting skills.
Group policies? What do you mean by that? All accesses to read, write or execute are handled by regular unix permissions or ACLs.
UNIX permissions are controlled by groups, group definitions are made available by means of a directory service.
Access toa given machine? Password file, or pasword table in a name service.
Single password? NIS+ or kerberos. Cached password in a laptop? Are you mad? Use a damn token that generates one time passwords.
Patch update policy? Make a repository with the latest packages to be installed, run a cron on each machine that installs these patches in a regular basis.
All of the above (and more) can be done in any Linux, Ubuntu included.
So what is your point exactly?
In Linux/UNIX I just move the machine where I need it and turn it on.
NFS servers will be there (findable using DNS), user information will be in a directory service (NIS/NIS+/LDAP) authentication will be in kerberos.
Machine is turned on in new location, get its IP and name from a DHCP server and of you go.
What is exactly the problem???