People especially economists compare buying a software with buying a car. But this isn’t true. Actually the purchase is comparable to buy a license to use a special car with many restrictions.
e.g. you can’t
- install it on as many pcs you want. In contrast everyone you trust and has driver license can drive your car
- modify it (just a very little).
- give it away/sell it
- cannibalize it after it stopped working (a broken car you can strip from useful components)
- go to a car dealer/repairshop of your choice (there are some movements in the car industry to restrict this either)
- disable advertisments (in the car world they are optionally for your car)
- have a choice which car you use. In software world nearly every company tries to lock in the users
One similarity is: you are the product.
Many people live from you by exploiting your nescience (in the car as in the software industry)
Sorry it was late yesterday. I rewrote this article:
Checklist adding a google account to android:
- deactivate Autosync by tapping on the email address (in accounts) and deactivating every sync option
- deactivate in google preferences: check device for malicious apps especially the option beyond that you send them data
This is why I cannot recommend Android. It’s a clear breach of trust (you see the first thing never if you don’t know it and google doesn’t say it anywhere that autosync is active by default)
As I said in my former blog post I wouldn’t recommend deriviates either (same hyper-commercial App community)
I think the same is true for IOS and Windows 8 smartphones.
What exists and looks good is firefox os. There are even some cheap smartphones. But I have no experience with it.
But I need App: xy
Install android-x86 in a virtual machine. I think it’s straigthforward so I don’t explain.
But be careful, don’t forget the checklist.
Anyway this is also a good way for non-smartphoner to have access to apps.
One difficulty is to install apps which doesn’t want be installed on tablets.
An approach is to install the apk file. Better would be to tricking android in believing a smartphone (sorry I didn’t find out how yet)
The Android userbase is an hostile environment for admins and developers. Even android is technically a very good idea (except java).
Firstly every problem is appified. You don’t get any usefull information about internal stuff (e.g. where files lay around) by searching after the problem. The solution for every problem is: install app xy (and boost the download score of someone).
Secondly most android developers come from the windows world. They don’t share for free. Saying: this world doesn’t give anything for free why should I do so? Many apps say: hey I fix this, but lacking information how they do it. Sadly there is no filter to filter them away.
Thirdly transferring knowledge is risky. Some important features/bugs could be “fixed”. Or you could get legal trouble. Even android is under gpl this discourages people from transferring knowledge.
Fourthly you get logged and recorded on every step. I never thought about the normal world implications: Every app you looked, you installed, deinstalled is haunting you. Not the secret services, but the companies. They push advertisment crap. On a small display this is especially annoying.
Fifthly some apps have advertisements. They put you into the risk of beeing hacked by their advertisment crap (happened often enough). Also eating your internet, display space and battery. Imagine this on your PC. Every 10 Minutes something pops up and annoys you. I hadn’t this for years (since I switched to linux).
(I heard from a prof that the internet speed improvements are mostly for advertisments (that the speed penalty by them is noticed less))
Problem: you can’t login even you have entered the right password..Then here is (hopefully) the solution:
Assumption 1: It is a problem with the login shell. You have to check three things:
- exists the shell? (Maybe the path is wrong)
the path is found in “/etc/passwd” (last column behind user account)
- is the shell readable? check via ls -l <pathtoshell>. There must be a “r” in every column (uncommon error)
- (most tricky) is the shell path in “/etc/shells”? It must be the “exact” path not a path which points to the same shell
Assumption 2: User account is locked
This problem is very easily fixable. Just enter (as root):
usermod -U <account name>
Assumption 3: it’s the user folder
There could be multiple problems with the user folder for the account
- does it exist? look in “/etc/passwd” (the second last column) if the path exist
- are the read write permissions of your home folder correct?
You have to check
1) the basedirectory (e.g. /home/laura)
2) the shell specific files (e.g. /home/laura/.bashrc)
3) (graphic login only) .xsession .xsession-error must be read writeable
Check this via ls -l and change the permissions via
“chmod 770 <path>”
- are you the owner? same as 2 (just watch the owner)
“chown <account name>[[:<usergroup of account>]] <path>”
You want to load a exception/domain file into tomoyo but you can’t because of some strange errors (exit with 1)?
And you are sure that tomoyo is loaded (has to be in the kernel bootline) and you ran tomoyo-initpolicy as root?
Here is the solution:
You may have not the permission to write into the /sys/…/tomoyo dir. You have to authorize some programs to do so.
Now check /etc/tomoyo/manager.conf. You see multiple paths. Now check if they are all real or went over links.
You can do this with realpath:
if the output is not the same as the input, then replace the path in the file with the output.Now reboot the PC (is needed to load the manager.conf) and now it should work
sometimes you need more than one object to produce smoke but hups? what’s that? Just one object produces smoke.
The solution and the reason for this problem are simple:both objects are in the same flow group
What’s flow group?
You can create for an object a group via:
pressing on the cube in the right side bar (where can preferences of objects)
then scroll down to groups and press on the + sign to create a new one
And now you have a group. To asign a smoke domain to a group go to the smoke menu and click into the field flow group, then assign the group with the right smoke producing object.
First forget the curse tools tomoyo gives to you. They are good but very limited
install tomoyo,( configure the kernel for tomoyo if your distribution hasn’t done it, here a guide:
run sudo /usr/lib/tomoyo/init-policy to init the config
and append security=tomoyo to the kernel boot line in grub.cfg (better: /etc/default/grub and update bootloader) or whatever
Create a rule for a program:
Important rule: name important resources with an speaking name, you can also insert comments with #
1. initialize_domain yourprogram from any
where x is the number of the ruleset.
an overview gives: http://tomoyo.sourceforge.jp/2.5/chapter-4.html.en
and load it with:
tomoyo-loadpolicy -df </etc/tomoyo/domain_policy.conf
basicly there are now two ways to develope now a ruleset
1. switch to policy 1, run the program, close it, save down the changes
2. use policy 2/3, run tomoyo-auditd and look in /var/log/tomoyo/rejected00 2 or 3.log what permissions the program needs to run.
for using wildmarks have a look in
add the new rules to domain policy and reload the config via:
tomoyo-loadpolicy -df </etc/tomoyo/domain_policy.conf
some links which will explain some aspects more detailed:
here you have a sample file:
With the normal navigation view you will have soon many problems. For example you cannot/can bad zoom into buildings, other objects.
So press shift-f to get an kick-ass view (navigation should be obvious but I explain it in detail: zoom – mouse wheel, left, right,up, down: mouse). Then press the left mouse button and switch back to the normal zoom mode in the new position or ESC to jump back to where you began to use the view.
problem was: my logitech c270 webcam had stripes wandering around, I think you could call it flicker. I tried everything but nothing helped. Just changing the resolution helped a bit.
now the real solution and the real problem: adjust via v4l2-ctl -c powerline_frequency the powerline frequency. The flickering immediately stopped for me. To see which values it can have use v4l2-ctl -L
for me worked:
v4l2-ctl -c powerline_frequency=1
It was simply the power supply!!! It has an other frequency in Germany than in the home country of logitech. The technicians saw this problem coming so include such an option but… they were too silent (should have dropped an entry in the FAQ explaining that).
Ok, I use linux and the tool of logitech would surely have adjusted this but I’m windows free.
If you play a bit with the configuration under /etc and you accidentally change the permissions of /etc/Networkmanager you can end up with no connection to the internet.
The problem is not too less permissions but too much:
– root with group root must own /etc/Networkmanager/system-connections and have the octal permissions 755
– and root with group root must own the files beyond this directory. But the octal permissions of the files have to be set on 700