Onze cypersgrijze halflangharige grote ex-kater is sinds de nacht 5 februari vermist in Transwijk Zuid – Park Transwijk (Utrecht). Hij ziet net als een Maine Coon eruit. Hij heeft een rood halsbandje. Niet gechipt. Gele ogen. Pluimstaart.
Als U hem (levend, gewond of dood) ergens heeft gezien, stuur mij aub een e-mail op alekz.net (apenstaartje) gmail.com
Zie foto's beneden.
Somebody That I Used to Know – Walk off the Earth (Gotye – Cover)
66,106,172 since Jan 05, 2012.
The original video below:
If UPnP devices do not see each other, most likely there are two problems:
Multicasts are not forwarded
Simple Service Discovery Protocol (SSDP) uses multicast IPv4 address 239.255.255.250. The local switches must be able to forward such traffic. On a Cisco switch you run the following command to allow that:
Firewall blocks UPnP traffic
Related ports: UDP-1900 and TCP-2869
In my mind universality and simplicity are mutually exclusive. I'm yet to find a system which is universal and simple to configure and use. Reliability and stability are assumed by default.
The simplicity of Apple devices is addictive. You add a new box and it gets automatically recognized. Everything just works like prescribed and defined by Apple. Then it's a question of if this Procrustean bed fits you or not and if you are flexible enough to assume the offered model.
The idea of service/device discovery appeared in the late 90's. For example, Sun's Jini (1998) and UPnP (1999). It's nice to have a standard to allow devices from different vendors work together, right? Sure, but here comes the reality. The Cisco interpretation of the Spanning Tree Protocol is different from the Foundry (now Brocade) one. If you place Cisco and Foundry switches/load balancers in one LAN, you may end up with a funny STP loop.
Solaris 11: root/solaris
Cyclades console servers (e.g. ACS4): root/tslinux
Avocent ACS5000 console servers: root/avocent
Cisco VPN3000: admin/admin
Cisco ASA: empty
Netscreen: netscreen/netscreen
Avocent/Cyclades PM IPDU: admin/pm8
Solaris 11 EA (Sep 2011 build 173) updated zpool version to 33:
$ zpool upgrade -v
This system is currently running ZFS pool version 33.
The following versions are supported:
VER DESCRIPTION
— ——————————————————–
1 Initial ZFS version
2 Ditto blocks (replicated metadata)
3 Hot spares and double parity RAID-Z
4 zpool history
5 Compression using the gzip algorithm
6 bootfs pool property
7 Separate intent log devices
8 Delegated administration
9 refquota and refreservation properties
10 Cache devices
11 Improved scrub performance
12 Snapshot properties
13 snapused property
14 passthrough-x aclinherit
15 user/group space accounting
16 stmf property support
17 Triple-parity RAID-Z
18 Snapshot user holds
19 Log device removal
20 Compression using zle (zero-length encoding)
21 Deduplication
22 Received properties (Solaris Nevada b130 Dec 2009)
23 Slim ZIL
24 System attributes
25 Improved scrub stats
26 Improved snapshot deletion performance
27 Improved snapshot creation performance
28 Multiple vdev replacements (ZFS for Linux)
29 RAID-Z/mirror hybrid allocator
30 Encryption
31 Improved 'zfs list' performance (Solaris 11 Express b151a Nov 2010)
32 One MB blocksize
33 Improved share support (Solaris 11 EA b173 Sep 2011)
Допустим, что мы не знаем, ни кто такой Вячеслав Полунин, ни чем от занимается, и попробуем определить его соционический тип (ТИМ) только по интервью и программе "Линия жизни" на телеканале "Культура" (эфир 24.06.2011).
Blog updates