File manager

File manager - Edit - /home/newsbmcs.com/public_html/static/img/logo/libfakeroot.tar

Back
README��0000644��00000001011�15027567035�0005427 0��ustar�00��fakeroot can be built to either use SYSV IPC or TCP for message passing. Cases for which the SYSV IPC version fails or causes problems but for which fakeroot-tcp has been observed to work well include the items listed below. * Multithreaded applications (using pthread) * Running under realtime-preempt kernel Portability Notes On OS X, only binaries that do NOT rely on Mach-based [e]uid/[e]gid/mode APIs will correctly use fakeroot altered ownership/permissions. See README_MACOSX.txt for further information. ��copyright��0000644��00000002124�15027567035�0006510 0��ustar�00��fakeroot contains code under the following copyrights and license: Copyright Ⓒ 1997, 1998, 1999, 2000, 2001 joost witteveen Copyright Ⓒ 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Clint Adams Copyright Ⓒ 2009 Regis Duchesne This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. The Fakeroot::Stat Perl module, Copyright (C) 2002-2007 THUS plc., is licensed thusly: This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. On Debian systems, the GNU GPL can be found at /usr/share/common-licenses/GPL-3 and the Artistic license can be found at /usr/share/common-licenses/Artistic ��changelog.Debian.gz��0000644��00000001704�15027567035�0010232 0��ustar�00��UYo�F~��&@�"�S�v}�� V�E`��r��Ö��;%[Il�)�� $�;�3gl�Z)�C?z��:i]��^�N�(��OB��\|gHO`�U �8�L��Ʋ�@�`͸䲄�b�D��d�X4�8n��M~�O\|�ypB�f��\��z5+%��P��Ψ�T�r�X��Kf{�p�4DAAfq�\|�A��3��-�;Z5��s��p��p%��̅+�@�l^u�/Y�P��S��HD��r�?�� K� ʐ2�@��4\p ��_��8oo>�{�9�M��,��0/H?�;�?9��#xEV�¸��ur�՝X+i�v�ﱵ�׍V�$�X��L��!L�`��V��ã�?>r8NG��$�`K�4�Y��pߣ��xY�eP�km��CM�Ŋ��1_�r�j\r�i�~��'�k �Q��5��g��>[Tr�դ��7��x��0K�o�:�R �+�}a�hր��P ��j��3!�H��UzL+'��$�jRL׃(�Q�[)B�Y8��!)o�?�%��Y8Ѫ��:�TD�TL;˅��E��H�W��_��0 ��ݮ�v��{p��>\b�Q��N(��'�S?n��b+�m��W^�K�q�(ڱ�.��p[�{c� 4�-�g�ڊ3���{j��}z{cW0��v�C��0��dW�8v�ʊk��md�>��VsxE^�)su �T�AwA:�c��AY:Ȓ�@��?��B�� `T�+M��D.į��8��u;_�0��`�qB�xq �Ì/ncWc�B��I��]2ţ`��-\|��AK�$��,�7<�c�A��k"�J@I��@; �Xc��:Q܈�l��+5 ��DEBUG��0000644��00000003520�15027567035�0005327 0��ustar�00��To debug fakeroot, one may try: Start faked in xterm 1: $ faked --foreground --debug 51452231:280 # First number here is the 'FAKEROOTKEY', second is the pid of # faked. Both to be used later. # Later, when programs go using faked, a _lot_ of debug output # will be shown here. Send signals to faked in xterm 2: #Whenever you want to get info about the internal inode data #faked is keeping, do: kill -s USR1 280 And the 'real' program runs (at your choise) in another xterm [3], or gdb In an xterm, do: $ LD_PRELOAD=/usr/lib/libfakeroot/libfakeroot.so.0 $ FAKEROOTKEY=51452231 # number output by faked, xterm 1 $ export LD_PRELOAD FAKEROOTKEY $ my-prog #start anything you like. Or, if you want to run the programme in a gdb session: To make specifying the paths easier, put libfakeroot.c, libfakeroot.so.0.0.1 and the binary you want to run in the same directory (libfakeroot.so.0.0.1 is put in ./.libs/libfakeroot.so.0.0.1 by libtool during compilation, copy it out there). Then, in gdb do: $ gdb ./ls #as an example, I run 'ls'. (gdb) set env LD_PRELOAD=/home/joost/maintain/vpathlib/libfakeroot-0.1/libfakeroot.so.0.0.1 (gdb) set env FAKEROOTKEY=51452231 #number from xterm 1. # Or wherever you've got your libfakeroot.so.0.0.1 (gdb) break libfakeroot.c:181 Breakpoint 1 at 0x4000ecc8: file libfakeroot.c, line 181. (gdb) run -al Starting program: /home/joost/maintain/vpathlib/libfakeroot-0.1/ls -al Temporarily disabling shared library breakpoints: 1 Breakpoint 1, __lxstat (ver=134556187, file_name=0x0, statbuf=0x80529c8) at libfakeroot.c:208 208 struct stat statbuf){ # OK, and there I've found a bug -- ver can only be '0' in the # current libc6 (glibc2). Unfortunately, it didn't reproduce. ��README.saving��0000644��00000005244�15027567035�0006731 0��ustar�00��The fakeroot environment can be saved for later use if you use the -s option to fakeroot. This will not work perfectly, however. Internally, faked keeps track of all files which have had operations done on them that the user would not normally be able to do, in order to fake the effect later. For example, if you create a device node, faked will actually create an empty file, but remember that it was a device node (along with the relevant details) so that if you subsequently do an "ls -l", you'll see it as a device node. The save option simply saves this list, so later fakeroot invocations can restore them. However, you can manipulate the files saved outside of the fakeroot environment (for example, you could delete the zero-length file that was the placeholder for the device node) and fakeroot will not know about it when it loads up the list again. This will cause the list to leak. The list cannot easily be verified, either, because it keys things by inode number, and there is no mechanism to look up anything from one of those alone. Such verification _could_ be done, but would in theory require a search through the _entire_ filesystem, every time. This isn't really acceptable for regular operation, and I don't need such a feature so I haven't written it. The file format is fairly straightforward and obvious, however, so if anybody else wants to... :-) So, this feature should only be used if you limit everything you do inside the fakeroot environment to the fakeroot environment. This is still useful - for example (assuming you have the appropriate key): $ fakeroot -s backup.environ # mkdir backup # cd backup # export RSYNC_RSH=ssh # rsync -a root@important.example.com:/ . [...] # exit $ Now, "fakeroot -i backup.environ" will get you exactly what you had backed up, user and group information, device nodes and everything. Of course, that information is still faked, but you should be able to happily rsync it back. This way you only need normal user privileges on the backup machine. This is great to back up multiple machines without a compromise affecting the backup machine and thereby compromising all the other machines you back up as well. Note that further rsync updates should be done with: $ fakeroot -i backup.environ -s backup.environ # cd backup # export RSYNC_RSH=ssh # rsync -a root@important.example.com:/ . [...] # exit $ so that further changes are still saved. In this scenario, the shortcoming will not affect anything, as the only modification of files which required root (and consequently were faked) is done inside the environment, and can therefore be tracked and saved. Have fun! Robie Basak <robie@principle.co.uk> Northern Principle Limited 25/3/2003. ��

| ver. 1.4 | Github | . | PHP 8.2.28 | Generation time: 0.02 | proxy | phpinfo | Settings