doukoula console login: pascal
Password: login account failure: No account present for user
instance svc:/system/console-login:default exited with status 1
What's the problem?
It is the nscd, the Name Service Cache Daemon.
What did I wrong?
When you wonder why your known_hosts file has changed or you don't find your hosts:
|1|AEf8B/QCP+1wRKA761Cq/woad4s=|HVEWXKDdRpZmO3GeQ5T37xCFwgE= ssh-rsa AAAAB3NzaC1
yc2EAAAABIwAAAQEAt20HN/iasjy9KEW/BGjtxlsy8oebyEEnZvKAnjMck0EEVbA5rtE4dzisnbrYwZ4
67JP+p9UGZDQa4jbVo2ZHmz28nQapmw1WpLBD2wSN66PsMk5QCxICxBC6PDCOlwakQvLNES2B9R2cuev
G9Ag2ni+2Qdb17gEkkh2MZ91INylAzM7QWW7soGoSf1TsshSHexfMt12zb6kWxRuRCeT4fOzlJNOmPgr
uE3wTt/kfEbvPBZwDyUbEKApfYIxO8ic+FyO7qFEjHkhqT7px/oJMLS279uUHlhG+KWtPxYPhWaYulPZ
hhdn4D6pR+6shjPsH4VTyAUGwf7usKUvJZP59Ww==
Then your ssh server software is a new version which hashes the known hosts file entries. To remove entries from there because the host key differs (you installed the host completely from scratch), just type:
ssh-keygen -R hostname
or
ssh-keygen -R ipadress
That's it.
If you have a new ssh package, you may hash yourself your known_hosts file by typing:
ssh-keygen -H
May many of your wishes may become true in 2012.
Just a short note:
It contains important fixes for PKCS11 handling of KMS (Crypto Key Management).
Apparently Android 2.2 is not capable of displaying arabic characters possible.
Has this changed in Android 2.3, 3.0 and 3.1?
If you accidentally upgraded your root zfs pool (which is not recommended until it is supposed to be done from Oracle) do not forget to update your boot signature, your boot archive and your grub installation -
but do not reboot before having done this, otherwise the system won't boot any more.
Don't upgrade the root pool! You won't be able to repair your system when booting from the actual Solaris 10 boot CD (09/10) as the root pool cannot be mounted then. The following steps are to make sure that your system will at least boot when you did the upgrade accidentally.
Example:
As you know, kissmetrics' tracking algorithm is based on the ETag resource sent along with every document from http servers. Its normal use is to distinguish cached documents from new versions, if the document to be delivered has altered a new ETag is generated. In web caches every cached resource is stored with its ETag.
For a request on a resource stored in the web cache a http header line like
If-None-Match: "H33jh3gggIU§gug3kjhgHhjbkc3"
will be added to the request which means "please send out the document only if its ETag is no longer H33jh3gggIU§gug3kjhgHhjbkc3".
kissmetrics generates ETags as User-IDs to be tracked and every site which uses kissmetrics to analyze web traffic data will include a small kissmetrics.com-request in their web site. The web browser cache will cache this little resource along with its ETag which is NOT its calculated ETag but the kissmetrics "user id". So on every site with a kissmetrics "bug" the request gets done with the
If-None-Match: "your_kissmetrics_user_id"
And voilà, you're tracked. Deleting cookies does not help. You have to clear your cache in your web browser after every site visited. Not very useful.
A possible solution would be to use a web proxy like squid which can easily filter out the "ETag" headers. So web browsers will use the "If-Modified-Since:"-method to make web servers to deliver documents only if they have changed. This will not work on most dynamic web sites however as web application programmers often forget to set and to honor this request header (using the last changed timestamp of the displayed data for example).
I will try it.
I'll begin on Wednesday. No more Macintosh, no more Windows - I chose Ubuntu 11.04 on a Fujitsu Siemens Esprimo PC with an Intel Core 2 Duo CPU running at 2,1 GHz. 4 GB RAM and a 500 GB Western Digital Enterprise Storage Hard Disk.
Not an expensive choice - I spent 150 Euros for the old PC, the new RAM and the new hard disk.
Will I be able to work day by day with this machine? Doing business? Watching movies? Playing games? Writing letters? Browsing the Internet? We'll see!
