1524011794 M * Bertl_oO  off to bed now ...
1524011795 N * Bertl_oO Bertl_zZ
1524029421 Q * FireEgl Ping timeout: 480 seconds
1524030009 J * FireEgl Fire_OFTC@2001:470:e56c:1:c816:a698:f8f5:e0b1
1524036993 Q * arekm Remote host closed the connection
1524037499 J * nikolay ~nikolay@external.oldum.net
1524037528 J * arekm ~arekm@phobos.pld-linux.org
1524041108 N * Bertl_zZ Bertl
1524041113 M * Bertl  morning folks!
1524049875 Q * romster Quit: Leaving
1524049961 Q * Aiken Remote host closed the connection
1524062758 M * Bertl arekm: any news regarding vanilla kernel + vs patch?
1524063251 J * romster ~romster@158.140.215.184
1524064798 J * trs ~trs@188.113.126.81
1524064997 M * trs hi ! does the patch-4.9.82-vs2.3.9.7.diff on 13floor include the delta-netlink-feat* or are the needed to be added after the main patch? (or needed at all on 4.9 ?)
1524065300 M * Bertl the feature patches are not part of 4.9.82-vs2.3.9.7
1524065327 M * Bertl they are for 4.4.x, but they might as well apply to 4.9.x
1524065427 M * trs right. Thanks! :)
1524065516 M * Bertl you're welcome!
1524065882 M * trs anonther issue: I made a question on the mailing list some weeks ago, but did not really get much wiser. It was about hashify and what it does (if anything) to handle CoW for files that orginally was hardlinked inside a vm (and then will be split inside the VM on CoW). Anyone (Daniel?) care to comment?
1524065904 M * trs anonther issue: I made a question on the mailing list some weeks ago, but did not really get much wiser. It was about hashify and what it does (if anything) to handle CoW for files that orginally were hardlinked inside a vm (and then will be split inside the VM on CoW). Anyone (Daniel?) care to comment?
1524065994 M * Bertl well, the problem with hard links is that you can't tell where they belong and you don't know how many there are
1524066060 M * Bertl i.e. a hard link is just another normal dir entry which points to the same blob of data
1524066100 M * Bertl there is no way to efficiently figure out where the other pointers are and more importantly where they belong to
1524066127 M * trs yes...  would it be an option not to hashify files that is already hardlinked to several places inside a vm=
1524066133 M * trs ?
1524066191 M * Bertl I think that's how it is currently done in util-vserver
1524066200 M * Bertl or at least there is an option for that
1524066228 Q * nikolay Quit: Leaving
1524066288 M * trs ok, guess the easiest way to figure this out is to test :)  
1524066435 M * Bertl also note that unless you plan to have a huge number of guests which share a lot of files/libraries/binaries there is little point for unification nowadays
1524066445 M * Bertl both disk space and memory is rather cheap
1524066491 M * trs our use case is a little special. we could have limited space but lots of VMs...
1524066537 M * Bertl another option is to create a list of all hard linked files before you unify and use the list as exception
1524066783 M * trs that was actually a good idea if it is not handled by hashify itself. 
1524066951 M * Bertl thanks, off for now ... bbl
1524066956 N * Bertl Bertl_oO
1524068231 J * sannes ~ace@2a02:fe0:c130:1d90:243a:5d81:2dad:3f61
1524068274 Q * sannes 
1524068289 J * sannes ~ace@2a02:fe0:c130:1d90:243a:5d81:2dad:3f61
1524068352 Q * sannes Remote host closed the connection
1524068418 J * sannes ~ace@2a02:fe0:c130:1d90:243a:5d81:2dad:3f61
1524070319 Q * trs Remote host closed the connection
1524070437 J * trs ~trs@188.113.126.81
1524082521 Q * FireEgl Ping timeout: 480 seconds
1524083111 J * FireEgl Fire_OFTC@2001:470:e56c:1:c816:a698:f8f5:e0b1
1524083513 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951
1524084760 M * Bertl_oO  off to bed now ... have a good one everyone!
1524084761 N * Bertl_oO Bertl_zZ