diff --git a/CHECKSUMS.md5 b/CHECKSUMS.md5 index 0c25895..b3dae91 100644 --- a/CHECKSUMS.md5 +++ b/CHECKSUMS.md5 @@ -10,12 +10,12 @@ tail +13 CHECKSUMS.md5 | md5sum --check | less /pub/gnu, or at any GNU mirror site. MD5 message digest Filename -0e45f4b5ce1adc62aa4cb33232eddc20 ./ChangeLog.rss -461a670f7361f6c8973c62e84df87809 ./ChangeLog.txt -37e4f4db8e9e77980f4e7a76d7c9d2a9 ./ChangeLog.txt.gz -7b83dbc289f0273d5419a5c185f32e6c ./FILELIST.TXT +f5238f30dca06ab6b1a31604110f3814 ./ChangeLog.rss +5f17e08a86354a5a91613bbb469b78ed ./ChangeLog.txt +86674f73abb76f778158bf16962700ce ./ChangeLog.txt.gz +65981f99487073cb35f4501fe8073582 ./FILELIST.TXT 7f4bffeb686cc5fd6056bd404dda08d7 ./GPG-KEY -3116d898061cf9c3396c917d80d2b77c ./MANIFEST.bz2 +b6b16f4804b51041242b6781ca0ecb4f ./MANIFEST.bz2 929e7c4ff15161d2fcba2057ec2a2f3a ./NetworkManager-fortisslvpn/HEADER.txt 929e7c4ff15161d2fcba2057ec2a2f3a ./NetworkManager-fortisslvpn/README 26bea576c23b7b122207b86e0ca4c67e ./NetworkManager-fortisslvpn/build/NetworkManager-fortisslvpn.SlackBuild @@ -28,8 +28,8 @@ MD5 message digest Filename 862766d751cd6bf0a92e6162bd329186 ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.tgz.asc d65495fb9b09ee9b0ede6c5903119dde ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.tgz.md5 10f078f71cb5fa957784abc1c53a70d4 ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.txt -0439c3c8652c32896278049edc508ba5 ./PACKAGES.TXT -5deacce1a9e742ddac1415d83a61a627 ./PACKAGES.TXT.gz +ab0a65ef67e8b83fc05a27dc2543ef53 ./PACKAGES.TXT +4d1dff6093a1b556233b1acd778b3b2e ./PACKAGES.TXT.gz c816a86246d3cc161cf2e869d16131bd ./audit/HEADER.txt c816a86246d3cc161cf2e869d16131bd ./audit/README 29eb321fa3b3c679ba8e4ae4b36a3809 ./audit/build/README @@ -551,16 +551,18 @@ d71863045ca687649982f4534099954d ./valgrind/pkg64/current/valgrind-3.17.0-x86_6 4bf76dc999a06a659ee0107d7820fd76 ./vde/HEADER.txt 4bf76dc999a06a659ee0107d7820fd76 ./vde/README e06e2ec44c43647da743ee65d58be371 ./vde/build/README -7dc14eebcc6923bfdd6abb9e90cb804c ./vde/build/VDE_HOWTO.txt +b68e19416bc2283678930e918c1463e9 ./vde/build/Using_VDE_with_QEMU_HOWTO.txt +c1fd62e426e7d306f19321d52955f194 ./vde/build/VDE_HOWTO.txt 1d5075dd0c0e0c3ca88901e645e32faf ./vde/build/rc.vdenetwork 4bf76dc999a06a659ee0107d7820fd76 ./vde/build/slack-desc d5f947a4e24b850687d49156eac09cd4 ./vde/build/vde.SlackBuild 165a0ea7f28a9de83a805770eee8e92a ./vde/build/vde.info -b71d5ad299c5c856822e4a23c0c42cce ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst -7e2bc5c12cfa5b83ccedfd0f352d6dec ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta -2c98ce79f27034eb98785cfed4e59bdc ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz -c16dd5bbd0830e981c26b7fec6efd1b1 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc -d9a41e0c9f186b220ac9d21b3f29dd08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 +46fbc5f97f03dc517aa3b2c9d9ea6628 ./vde/build/vde2-2.3.2.tar.bz2 +064da38cd920b7bea642de7404afb677 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst +395472b574825fc74807ca6ccea0a969 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta +ce63d20ab5959b6a98d30d37f448bbab ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz +1b9c94dfa8453e554e7b11ca26243b50 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc +1a21cd7e2f9facdca3f7d9e67a7fb650 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 30f4fb3eff5387c255813407af5375e5 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.txt 89f1f7294949d150af49cacf3c4adb9a ./virglrenderer/HEADER.txt 89f1f7294949d150af49cacf3c4adb9a ./virglrenderer/README diff --git a/CHECKSUMS.md5.asc b/CHECKSUMS.md5.asc index 6ef2dbb..bfec384 100644 --- a/CHECKSUMS.md5.asc +++ b/CHECKSUMS.md5.asc @@ -1,17 +1,17 @@ -----BEGIN PGP SIGNATURE----- -iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWxPgZHGd6YW11ZGlv -QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZVxwuD/9I+cGoN2zbg1BaqNJ16TqA -6wDxzr5T0BFan7XY5ulUGYLAeyyOjnH/DgwaufW3MThkWUuDLsal+vYFvZAM417Y -jvt0P0asTOS0R/tLLX+8mmIILM2L616b7LhgeBzX9+bXYYd5mDeWGfs73E87Jtad -fIdEd4MIczkSnYA2W13nQDUay8Ig+x9t7PYhjkzmGSE0rG0ECcQvpxyUt/0xRrWf -Eqqkj9f6PSGX3CXKN95grOGzxCfogLPUrxjyufSSx5aJkGRTHci7zNEnzTnWcOxf -mmBFzdfx2u9U7JhkgAnZTTsHMJ08yRn3Ds1U8C74J0tgs5NtyMpc8PBEk2O7w07p -PrP3FcvPgnwdj9kRcmqyJGr4XijopzyXJZ4scUXwZvdmJel+gfvC3Eu215yTCBKn -jpxFeYRGKERdYIeqkNlHQfMrAQbJzlIFxchihHRZpwaUYHoi4Hl96HFV+YaZePRb -oBww+qdJl8pFAd9TxB2gWednHd0IZ7ZmCcJwGpFbRSVhfIA+9C+aaynFLVhblmoX -ctqyWvTdLIe+7ISFbPmN4A/b7VFoziysE3TO76JA11A1ScsyMgfZcdclcUhty0vB -20kyX6waMslN3FEahrAw1PMCn62v+iFnuiufA/DK2nHnjEZlGcbsvlF8tT5+/PU4 -gNsteaFdw60rx4ob0ZhVRQ== -=Liap +iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv +QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV9S2D/9LGUjWjVUaFB6rw9el+n6C +rVcQeOZNjLpQc9yIDTtVFV9aQYZNOPWJUx9A+w19Tjpi4Q2Ge5W6fQnnwPy++AQl +nLgoAEJ5FNeU1uszLJ7Ozf/yDELXYQuLoWtY/j9SPZY4beI5bUv2PoY8m/SK0t9y +PSp2k6h99cPSgOno8l6gUFGV6meJr8SnnytA9ArRRNxMdZ9xwdGN0fGNX6kspANV +g7VAUbQmylEL4CrHhyulafZg5zLjdozxsoAZt3A50DKmUR+qxxhaj+EveInhsxa2 +9ms+wofDkKE5m6AfxCbf5G6YIwYjdWcVQ1ySztivkwMxHaTApR84E1h5hgF0IqfL +GHLKVGgfNCL6Y/4WshQ2auK/rEClm3m2Sw9YVfQbxI9PiGOcY1xgb4M/9zUYKwQR +cMtKmSWn2TcMZYDNCtl1ckSEftKPpRxOyopJgKR8gb5vk7lbqOD7sO3WiLlfPTKT +Rvj49Pv6NoyHuQUQFnqGEO5VFnWOBWqeDH4cZ90PLnuF/wNW+vLdIqHJieEzQchI +DZOXML8RAzOJNuCe4KypLc02GSr39X2bt7J1CFSkyyTT9bJNEKbYROx0+gesaRs8 +Y0GWM5fWsjp63qBTlOxjiGQUtPvGfH4qIt9U/Ue3GfS02kTUvTpZ37oEvcoNTg9P +xaTzmhnurUNrALoJfCU6yg== +=AnOF -----END PGP SIGNATURE----- diff --git a/CHECKSUMS.md5.gz b/CHECKSUMS.md5.gz index 5ca2bf9..4de9af0 100644 Binary files a/CHECKSUMS.md5.gz and b/CHECKSUMS.md5.gz differ diff --git a/CHECKSUMS.md5.gz.asc b/CHECKSUMS.md5.gz.asc index 3866520..6bd78bd 100644 --- a/CHECKSUMS.md5.gz.asc +++ b/CHECKSUMS.md5.gz.asc @@ -1,17 +1,17 @@ -----BEGIN PGP SIGNATURE----- -iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWxPgZHGd6YW11ZGlv -QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV7ViD/9KFPDO0FEq6DAPpjIrP48c -HGkK8azkKty0v5jNkaQWVIMF8UpeVneeqlsFEr04whW1fpaVk4Ru6ntTKswumICl -m+Srt59N/AyhN/BtGxTZJxBgVP/0Tj5B6KL087BJ/zUAoNfSL0GppKif+JaahSKT -1vwda8dyJ5aHGZqZC0N8435TVE4z/9YbbfSPgABIXvqIHdHQiWvnDLGc8nbnsQI5 -//SqV6RyJTGCBNHhIERfCqCf/3CW8rUBMxzj3KxIRQ9zBjKBttpn2eDt1id6XfdX -OSVZzq4i6VPC/EJ+c88nagU7lK5NbIZc30JzJXdIkVJUOTmqzLzXy5iu7ywWAkez -ROBppnhLwoXQ/aT+AHCpakYfOc8MYq/Yl3f2U6VsxrfccC0MkjnWLbZA6gMH6VgP -9nGd8nfpw4r4H2fvkP1ESyZAqqcqtka0Fh7Y+HTx1zUL/+z8mLBdMLPZkYxeqR9A -uIpMd87Ob3g5mets9nHO0aBdkHaOcYYFUFs6pUGrJCy3sM5/U6+Kaj37KfGWgF15 -2fFim9iN510L4yW4Z1zzoRVmYGW68/PVTHd3KFnI1LF8vnRkY1b9nCZYLgxfoGRo -tTF2iDCJkYuZLTprR1piyuGHBpG8iLTNqd9uIiUdF4Kf+QKT2dRN9N27CAAr6hR5 -HbSBsF2vE1Cv+JkqF30Gyw== -=USM6 +iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv +QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV06ND/4tCq/Dhr9BVaylTFvm706y +hCdeIyD9NuaSPwk3Zc1RC+MoiJ9yfwoK0p44HneWJRHcCBfRKXwdkbw+zEj9/6o7 +O0YCaBgR2tasychDEazRXFg31YRVKkKJzNUWFomMyBo9SlJd85H4kpKEk3gYaH8V +c0h8wmHKrDOyMN0r3Gu1JBhEe2TSMRilssGz6VjNZ1tZDUiQkwXovY9KBx4KZn8G +2Ht+TG/SlVzcdo9XIwFS5oomhN7qHhQMxeSXEe+Rs4W0lBLcWnDnVSygtDhoRfj7 +auEF7lnuvSWdpYFbi2DnxVvYbGgq7OsxUZUVfsxHvif+y3yQjXXBau/zS+oPqwqX +NLb6lUkNBgylL9CLQ6RnhFEQRf0il/F2TqpXfHH6q+kqavXyd/oFA3DfKylLFwnT +owuZOx5RFeMx6qVHgGWWbTtduSwJnPIDZBgcWJCUzl2Cu4yU0dX8wswXVgLz+ns/ +TB7CjWZ+kI2Sz4fxc215oG2HCOucooq25/4e4Y5V0cAekBntOwJ72GxziYLefn5p +TW6lkHNQSkaRI2wFT+VyVFl8/C2ePNChbn19D7CgD/v2nXrhDhV6/ijK7Cxo2Nu9 +XClmFMUeuPf9FDFTneGmFMBbPtmMhGkeMSAWfQInzz2gjui2I1zH1PCnOTj5ikzt +CtNdW/6LEByL13jO11VTjA== +=XNVH -----END PGP SIGNATURE----- diff --git a/ChangeLog.rss b/ChangeLog.rss index 3921d25..dbf9f7c 100644 --- a/ChangeLog.rss +++ b/ChangeLog.rss @@ -11,10 +11,21 @@ Repositorio de software para Slackare Linux proporcionado por Libre Expresión México en-us urn:uuid:f735159c-86bd-11ea-9d48-04d4c453db33 -Sat, 8 May 2021 17:05:43 GMT -Sat, 8 May 2021 17:05:52 GMT +Sat, 8 May 2021 17:28:22 GMT +Sat, 8 May 2021 17:28:36 GMT gen_repos_files.sh v 1.98 +Sat, 8 May 2021 17:28:22 GMT +https://mirror.slackware.mx/libremex/slackbuilds/ChangeLog.txt +Sat, 8 May 2021 17:28:22 GMT +20210508122822 + + +vde: Recompilar +]]> + + + Sat, 8 May 2021 17:05:43 GMT https://mirror.slackware.mx/libremex/slackbuilds/ChangeLog.txt Sat, 8 May 2021 17:05:43 GMT @@ -190,16 +201,5 @@ libnfs: Recompilar ]]> - -Sat, 1 May 2021 23:51:22 GMT -https://mirror.slackware.mx/libremex/slackbuilds/ChangeLog.txt -Sat, 1 May 2021 23:51:22 GMT -20210501185122 - - -device-tree-compiler: Recompilar -]]> - - diff --git a/ChangeLog.txt b/ChangeLog.txt index 28f0a9d..027f62f 100644 --- a/ChangeLog.txt +++ b/ChangeLog.txt @@ -1,3 +1,7 @@ ++--------------------------+ +Sat May 8 17:28:22 UTC 2021 +vde: Recompilar + +--------------------------+ Sat May 8 17:05:43 UTC 2021 gtk-vnc: Actualizar a versión 1.2.0 diff --git a/ChangeLog.txt.gz b/ChangeLog.txt.gz index 63969c8..b095b07 100644 Binary files a/ChangeLog.txt.gz and b/ChangeLog.txt.gz differ diff --git a/FILELIST.TXT b/FILELIST.TXT index df5c5df..aa1fa2e 100644 --- a/FILELIST.TXT +++ b/FILELIST.TXT @@ -1,4 +1,4 @@ -Sat May 8 17:05:43 UTC 2021 +Sat May 8 17:28:22 UTC 2021 Here is the file list for https://mirror.slackware.mx/libremex/slackbuilds , maintained by Gerardo Zamudio . @@ -6,17 +6,17 @@ If you are using a mirror site and find missing or extra files in the subdirectories, please have the archive administrator refresh the mirror. -drwxr-xr-x 46 1000 100 4096 2021-05-08 12:06 . --rw-r--r-- 1 1000 100 46275 2021-05-08 11:53 ./CHECKSUMS.md5 --rw-r--r-- 1 1000 100 870 2021-05-08 11:53 ./CHECKSUMS.md5.asc --rw-r--r-- 1 1000 100 14203 2021-05-08 11:53 ./CHECKSUMS.md5.gz --rw-r--r-- 1 1000 100 870 2021-05-08 11:53 ./CHECKSUMS.md5.gz.asc --rw-r--r-- 1 1000 100 6250 2021-05-08 12:05 ./ChangeLog.rss --rw-r--r-- 1 1000 100 17429 2021-05-08 12:05 ./ChangeLog.txt --rw-r--r-- 1 1000 100 2475 2021-05-08 12:06 ./ChangeLog.txt.gz --rw-r--r-- 1 1000 100 311 2021-05-08 12:06 ./FILELIST.TXT +drwxr-xr-x 46 1000 100 4096 2021-05-08 12:28 . +-rw-r--r-- 1 1000 100 46346 2021-05-08 12:06 ./CHECKSUMS.md5 +-rw-r--r-- 1 1000 100 870 2021-05-08 12:06 ./CHECKSUMS.md5.asc +-rw-r--r-- 1 1000 100 14215 2021-05-08 12:06 ./CHECKSUMS.md5.gz +-rw-r--r-- 1 1000 100 870 2021-05-08 12:06 ./CHECKSUMS.md5.gz.asc +-rw-r--r-- 1 1000 100 6233 2021-05-08 12:28 ./ChangeLog.rss +-rw-r--r-- 1 1000 100 17504 2021-05-08 12:28 ./ChangeLog.txt +-rw-r--r-- 1 1000 100 2487 2021-05-08 12:28 ./ChangeLog.txt.gz +-rw-r--r-- 1 1000 100 311 2021-05-08 12:28 ./FILELIST.TXT -rw-r--r-- 1 1000 100 6217 2020-05-23 23:52 ./GPG-KEY --rw-r--r-- 1 1000 100 50856 2021-05-08 12:06 ./MANIFEST.bz2 +-rw-r--r-- 1 1000 100 50917 2021-05-08 12:28 ./MANIFEST.bz2 drwxr-xr-x 4 1000 100 4096 2020-05-23 23:54 ./NetworkManager-fortisslvpn -rw-r--r-- 1 1000 100 981 2020-05-23 23:54 ./NetworkManager-fortisslvpn/HEADER.txt -rw-r--r-- 1 1000 100 981 2020-05-23 23:54 ./NetworkManager-fortisslvpn/README @@ -33,8 +33,8 @@ drwxr-xr-x 2 1000 100 4096 2020-05-23 19:03 ./NetworkManager-fortisslvpn/pk -rw-r--r-- 1 1000 100 870 2020-05-23 19:03 ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.tgz.asc -rw-r--r-- 1 1000 100 85 2020-05-23 19:03 ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.tgz.md5 -rw-r--r-- 1 1000 100 474 2020-05-23 19:03 ./NetworkManager-fortisslvpn/pkg64/current/NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.txt --rw-r--r-- 1 1000 100 29995 2021-05-08 12:06 ./PACKAGES.TXT --rw-r--r-- 1 1000 100 7451 2021-05-08 12:06 ./PACKAGES.TXT.gz +-rw-r--r-- 1 1000 100 29995 2021-05-08 12:28 ./PACKAGES.TXT +-rw-r--r-- 1 1000 100 7453 2021-05-08 12:28 ./PACKAGES.TXT.gz drwxr-xr-x 4 1000 100 4096 2021-04-25 04:28 ./audit -rw-r--r-- 1 1000 100 884 2021-04-25 04:28 ./audit/HEADER.txt -rw-r--r-- 1 1000 100 884 2021-04-25 04:28 ./audit/README @@ -712,21 +712,23 @@ drwxr-xr-x 2 1000 100 4096 2021-05-02 00:26 ./valgrind/pkg64/current drwxr-xr-x 4 1000 100 4096 2020-05-25 19:30 ./vde -rw-r--r-- 1 1000 100 808 2020-05-23 23:52 ./vde/HEADER.txt -rw-r--r-- 1 1000 100 808 2020-05-23 23:52 ./vde/README -drwxr-xr-x 2 1000 100 4096 2020-05-23 23:52 ./vde/build +drwxr-xr-x 2 1000 100 4096 2021-05-08 12:25 ./vde/build -rw-r--r-- 1 1000 100 214 2020-05-23 23:52 ./vde/build/README --rw-r--r-- 1 1000 100 7032 2020-05-23 23:52 ./vde/build/VDE_HOWTO.txt +-rw-r--r-- 1 1000 100 11325 2005-02-09 10:16 ./vde/build/Using_VDE_with_QEMU_HOWTO.txt +-rw-r--r-- 1 1000 100 7922 2021-05-08 12:23 ./vde/build/VDE_HOWTO.txt -rw-r--r-- 1 1000 100 6345 2020-05-23 23:52 ./vde/build/rc.vdenetwork -rw-r--r-- 1 1000 100 808 2020-05-23 23:52 ./vde/build/slack-desc -rw-r--r-- 1 1000 100 8427 2020-05-23 23:52 ./vde/build/vde.SlackBuild -rw-r--r-- 1 1000 100 317 2020-05-23 23:52 ./vde/build/vde.info +-rw-r--r-- 1 1000 100 600527 2011-11-23 10:54 ./vde/build/vde2-2.3.2.tar.bz2 drwxr-xr-x 3 1000 100 4096 2020-05-23 15:45 ./vde/pkg64 -drwxr-xr-x 2 1000 100 4096 2020-05-23 23:08 ./vde/pkg64/current --rw-r--r-- 1 1000 100 3074 2020-05-23 23:08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst --rw-r--r-- 1 1000 100 591 2020-05-23 23:08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta --rw-r--r-- 1 1000 100 51942 2020-05-22 21:57 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz --rw-r--r-- 1 1000 100 870 2020-05-23 23:08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc --rw-r--r-- 1 1000 100 60 2020-05-23 23:08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 --rw-r--r-- 1 1000 100 354 2020-05-23 23:08 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.txt +drwxr-xr-x 2 1000 100 4096 2021-05-08 12:28 ./vde/pkg64/current +-rw-r--r-- 1 1000 100 3170 2021-05-08 12:28 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst +-rw-r--r-- 1 1000 100 591 2021-05-08 12:28 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta +-rw-r--r-- 1 1000 100 55865 2021-05-08 12:26 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz +-rw-r--r-- 1 1000 100 870 2021-05-08 12:28 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc +-rw-r--r-- 1 1000 100 60 2021-05-08 12:28 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 +-rw-r--r-- 1 1000 100 354 2021-05-08 12:28 ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.txt drwxr-xr-x 4 1000 100 4096 2020-05-25 19:31 ./virglrenderer -rw-r--r-- 1 1000 100 784 2020-05-23 23:52 ./virglrenderer/HEADER.txt -rw-r--r-- 1 1000 100 784 2020-05-23 23:52 ./virglrenderer/README diff --git a/MANIFEST.bz2 b/MANIFEST.bz2 index eec591d..37d0655 100644 Binary files a/MANIFEST.bz2 and b/MANIFEST.bz2 differ diff --git a/PACKAGES.TXT b/PACKAGES.TXT index 684c702..241a224 100644 --- a/PACKAGES.TXT +++ b/PACKAGES.TXT @@ -1,4 +1,4 @@ -PACKAGES.TXT; Sat May 8 17:05:43 UTC 2021 +PACKAGES.TXT; Sat May 8 17:28:22 UTC 2021 PACKAGE NAME: NetworkManager-fortisslvpn-1.2.10-x86_64-1_lem.tgz PACKAGE MIRROR: https://mirror.slackware.mx/libremex/slackbuilds @@ -723,8 +723,8 @@ valgrind: PACKAGE NAME: vde-2.3.2-x86_64-1lem.tgz PACKAGE MIRROR: https://mirror.slackware.mx/libremex/slackbuilds PACKAGE LOCATION: ./vde/pkg64/current -PACKAGE SIZE (compressed): 52 K -PACKAGE SIZE (uncompressed): 200 K +PACKAGE SIZE (compressed): 56 K +PACKAGE SIZE (uncompressed): 210 K PACKAGE DESCRIPTION: vde: vde (virtual distributed ethernet) vde: diff --git a/PACKAGES.TXT.gz b/PACKAGES.TXT.gz index 521e2bd..57618e0 100644 Binary files a/PACKAGES.TXT.gz and b/PACKAGES.TXT.gz differ diff --git a/vde/build/Using_VDE_with_QEMU_HOWTO.txt b/vde/build/Using_VDE_with_QEMU_HOWTO.txt new file mode 100644 index 0000000..7b59961 --- /dev/null +++ b/vde/build/Using_VDE_with_QEMU_HOWTO.txt @@ -0,0 +1,284 @@ +============================================================================= +This HOWTO originally appeared on: +http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00067.html +============================================================================= + +Using VDE with Qemu HOWTO +by Jim Brown +5 Oct 2004 +Version 0.2 + +----------------------------------------------------------------------------- + +Introduction + Copyright + What is qemu? + What is VDE? + +Configuring and Installing VDE + Installation + vdeq & vdeqemu + +User-mode networking + How to enable user-mode networking + Firewall configuration + +Slirp (rootless) networking + What is slirp networking? + How to enable slirp networking? + +Setting up qemu + How to set up the guest OS + +Credits + +----------------------------------------------------------------------------- + +Introduction + +Copyright + +Copyright (c) 2004 Jim Brown. +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.2 +or any later version published by the Free Software Foundation; +with no Invariant Sections, no Front-Cover Texts, and no Back-Cover +Texts. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt + +What is qemu? + + Qemu is a FAST! processor emulator by Fabrice Bellard, available at +http://fabrice.bellard.free.fr/qemu/. It is capable of emulationg the x86 and +PowerPC processors with support for other processors on the way. The original +purpose of qemu was to allow running x86-specific Linux applications, such as +WINE or DosEmu, on non-x86 systems. However, qemu has expanded into becoming +a full-fledged emulator. On the x86 side, it is capable of running Linux, +MS-DOS, Windows 95/98/Me, Windows NT/2k, Windows XP, Solaris, OpenBSD, and +FreeBSD. See http://fabrice.bellard.free.fr/qemu/ossupport.html for the full +listing. + + This howto assumes that you have already installed and set up qemu. + +What is VDE? + + VDE is short for Virtual Distributed Ethernet. VDE, written by +Renzo Davoli, is based off of uml_switch by Jeff Dike. It is available at +http://sourceforge.net/projects/vde/. It has many uses, the main one providing +support for networking with emulated computers. (Not just qemu, but support +for user-mode linux and Bochs also exists). VDE must be set up and installed by +root, but the programs which use it do not need root privligies. + + This howto will walk you through the simple process of installing +VDE and setting up qemu to use it. + +----------------------------------------------------------------------------- + +Configuring and Installing VDE + +Installation + + You may obtain the source code at http://sourceforge.net/projects/vde/. +The version of VDE which I used was 1.4.1, but this HOWTO should apply to all +versions. + + Once you have downloaded the source code, extract it. I assume you +will have extracted it to /space/vde. Go into that directory, and simply type +"make" followed by "make install". Now you should have vde_switch in /usr/bin. + +vdeq & vdeqemu + + Now cd into the qemu directory. Type "make". This will build vdeq. +Qemu on its own only supports full networking with tuntap, which requires +root priviliges or an exposed /dev/net/tun. There is a -user-net option, but +that is not as useful as full networking. In order for qemu to use VDE, it must +be passed the file descriptor for a tun device. Futhermore the tun device itself +must already be configured to use VDE. vdeq sets this up and passes it to qemu +via the -tun-fd switch. + + There is no "make install". Instead, you just manually copy vdeq to +/usr/bin. It might also be helpful to copy or link vdeq to vdeqemu. vdeq +requires that the location of the qemu binary be passes to it as the first +command line parameter, but vdeqemu only needs the options you want to pass to +qemu. vdeqemu will locate the qemu binary itself (this requires that you install +qemu system-wide or have the qemu directory in your PATH). + +For example if you have: +vdeq qemu -hda /mnt/myimage -m 64 -boot a + +you can shorten this into + +vdeqemu -hda /mnt/myimage -m 64 -boot a + +----------------------------------------------------------------------------- + +User-mode Networking + +How to enable user-mode networking + + The following commands will need to be run as root: + +# vde_switch -tap tap0 -daemon + +If you need to run a sniffer, just in case you want to analyze the traffic, +you can also run it like this: + +# vde_switch -hub -tap tap0 -daemon + +(The -hub option is not available for version 1.4.1 of VDE, you will need a +later version. I don't know what the minimal version is but 1.5.1 does support +this option.) + +Then you must run this: + +# ifconfig tap0 +# chmod 755 /tmp/vde.ctl + + The vde_switch command will run VDE in the background. The -tap tap0 +parameter tells VDE to set up the device tap0 using tuntap. -daemon runs +vde_switch in the background. -hub tells VDE to broadcast the message to all +segment, just like real hub that you use on real network. + + is the ip address of the gateway you want to use for the guest +OS(es). For example: + +# ifconfig tap0 192.168.254.254 + + will make 192.168.254.254 the gateway between guest and host, and your +guest OS(es) will belong to the subnet 192.168.254.0 with a netmask of 255.255.255.0 +and an ip address of 192.168.254.XXX (where you get to pick the XXX). You must have +the IP of the qemu guest and the IP of the gateway on the same subnet! While it +may be possible to have them on separate subnets, it will certainly be harder +to configure (and you won't like the way your routing tables will look either). + +[Sidebar: The "gateway" is actually the host OS itself on the tap0 interface. +The host on the tap0 interface, aka 192.168.254.254, routes between the guest +OS and the host's eth0 interface (which on is the real network). The host on the +eth0 interface (ex. 192.168.0.2) can then route between the tap0 interface and +the real network / the internet.] + +(Note that you might be required to do this: + +# ifconfig tap0 192.168.254.254 netmask 255.255.255.0 + +Normally ifconfig should pick the correct netmask for you, but if it doesn't +for some reason then you will have to specify it manually. See ifconfig(8) for +details. + +) + +Note that you must run this before you run your firewall. I found it helpful +to put this into a script, and have the script load before the firewall does. + +Firewall configuration + + You will need to enable masquerading between tap0 and your local area +network (for example, eth0). You will also need to enable masquerading between +tap0 and ppp0 if you use a dialup connection to the internet. The commands + +# echo "1" > /proc/sys/net/ipv4/ip_forward +# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE +# iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE + + will allow you to enable this manually. + +----------------------------------------------------------------------------- + +Slirp networking + +What is slirp networking? + +Slirp was an early program that existed before the masses knew of the internet. +Back then, those who knew of it could access it only in one way: through a +Unix shell account (or other such terminal account). This meant that one had to +do all the things they wanted to in that terminal window. Back then, there were +two dial up protocols: PPP and SLIP. PPP is now the standard but back then SLIP +was more common (as it was cheaper). + +Slirp was designed to turn those shell accounts into SLIP connections. It worked +by converting SLIP packets into socket connections. What you had to do was to +run slirp on the computer you had the shell account on, and then connect your +SLIP driver/dialer to the terminal slirp was running on (normally this +'terminal' was in fact a modem). Slirp would then interpret the data that SLIP +sent and transfer the data between the user's computer and the internet. To +the user, it looked like they were actually connected directly to the internet +through a firewall. + +Slirp is not used today (to the best of my knowledge) but the innovative idea it +had is used by both qemu and vde. Instead of converting SLIP packets however, +they convert ethernet packets. qemu's slirp networking is similar to vde's +but it is simpler to use and also limited to a single qemu instance (you can +not link multiple guest OSes together on the same network with slirp networking +unless you use VDE). + +How to enable slirp networking? + +This is very similar to TUNTAP networking in the previous section, but the +commands are slightly different. In addition, you do not need to set up +routing or firewall rules. + +First off, you load vde_switch (no parameters are required for this case, +although you can pass the -unix parameter if you want to use a different +socket - required if you already have tuntap networking on the default +socket). + +vde_switch + +or + +vde_switch -unix /tmp/unx.ctl + +The latter is required if you are running both slirp and tuntap or multiple +slirp networks (for that matter, if you are running multiple tuntap networks). +More on that later. + +Now you need the slirpvde command. slirpvde is the utilitry that provides the +slirp functionality - it intercepts ethernet packets on the network and +forwards them through the real network via emulation. To use it, you want +to do this: + +slirpvde -s /tmp/unx.ctl -n 192.168.2.0 -d + +The -s tells slirpvde that vde_switch is running on /tmp/unx.ctl [this switch +can be omitted if you called vde_switch by itself]. The -d switch tells +slirpvde to emulate a DHCP server. This is not required but it allows for +automatic configuration of the guest OS (it is basicly the same as qemu's +builtin DHCP server). Depending on your needs, you may be better off running +a real DHCP server in one of the guest OSes. + +The last option, -n, tells slirpvde +what subnet the network should be on (this is also used by the DHCP server to +figure out what ip addresses to assign). The gateway ip when using slirpvde +is X.X.X.2 (where X.X.X equals the first 3 parts of the subnet you passed to +it via -n, in this example 192.168.2) and the default DNS server is X.X.X.3 + +You can not change the gateway ip to something other than .2 and the DNS ip +to something other than .3 unless you change the source in slirpvde and +recompile. + +----------------------------------------------------------------------------- + +Setting up qemu + +How to set up the guest OS + + Set up the guest OS so that the default route is through the gateway +ip, (for example 192.168.254.254). Also set up the subnet and netmask +parameters as appropriate (for example 192.168.254.0 and 255.255.255.0). +The guest OS should see the ethernet device and be able to use it to access +the gateway. (Caveat: I haven't been able to do this for MS-DOS, and for Minix +2.0.4 I had to apply a patch to qemu since Minix is broken. Uodate: Minix 2.0.4 +is still broken but a patch has been released to fix it. Using this patch, +Minix works on a vanilla qemu.) Also don't forget to set up the IP of the guest +OS itself (for example 192.168.254.1). + +----------------------------------------------------------------------------- + +Credits + + This HOWTO relied heavily on the documentation that Renzo wrote for +vde-1.4.1. + Thanks to Mulyadi Santosa for helping with the first revision of +this document, and to Renzo for his input. (P.S. Will add info for ale4net +and slirpvde as soon as I figure out how to use it ;) + + diff --git a/vde/build/VDE_HOWTO.txt b/vde/build/VDE_HOWTO.txt index 73f2b85..6d0931c 100644 --- a/vde/build/VDE_HOWTO.txt +++ b/vde/build/VDE_HOWTO.txt @@ -1,80 +1,110 @@ -VDE : Virtual Distributed Ethernet. +VDEv2: Virtual Distributed Ethernet. -(c) 2003/2004/2005 Renzo Davoli -Based on uml-router Copyright 2002 Yon Uriarte and Jeff Dike +(c) 2003/2004/2005/2006 Renzo Davoli +Long long time ago based on uml-router Copyright 2002 Yon Uriarte and Jeff Dike qemu-vde-HOWTO is (c) by Jim Brown +Notice: Virtual Distributed Ethernet is not related in any way with +www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" +i.e. the German "Association for Electrical, Electronic & Information +Technologies"). Components of the VDE architecture: - - VDE switches: virtual counterpart of ethernet switches. - VDE cables: virtual counterpart of a crossed-cable used to connect two switches. +- VDE 2 includes: +- switch management both from console and from a "unix socket terminal" +- VLAN 801.1q *almost* compatible +- FSTP (fast spanning tree) already incomplete and currently not tested for 802.1d/w/s + compatibility. under development. (vde_switch must be compiled with the FSTP flag on) + Using VDE: -All units connected to the VDE see each other as they were on a real ethernet. -A real Linux box can be connected to the VDE using a tap interface (TUNTAP) (packets can be further routed using standard linux methods). -It is possible to join two VDE switches -- also running on different real conputers -- using virtual VDE cables -UML (user-mode-linux) virtual machines can be connected to the VDE -MPS (MIPS emulated machines (c) Morsiani/Davoli) can be connected to the virtual VDE. +- All units connected to the VDE see each other as they were on a real ethernet. +- A real Linux box can be connected to the VDE using a tap interface (TUNTAP) + (packets can be further routed using standard linux methods). +- It is possible to join two VDE switches -- also running on different + real conputers -- using virtual VDE cables +- UML (user-mode-linux) virtual machines can be connected to the VDE +- MPS (MIPS emulated machines (c) Morsiani/Davoli) can be connected +to the virtual VDE. Examples of VDE uses: -- With VDE it is possible to create a virtual network of UML machines running on several real computer +- With VDE it is possible to create a virtual network of UML machines running +on several real computer - VDE can be used to create tunnels (even crossing masquerated networks) -- VDE can provide mobility support. Changing a VDE cable with another does not affect the communications in place. The new VDE cable can use a completely different path on the real net. VDE supports also multiple concurrent VDE cablesbetween a pair of VDE-switches during the hand-off. This eliminates when possible hich-ups of communications due to hand-offs. +- VDE can provide mobility support. Changing a VDE cable with another does not +affect the communications in place. The new VDE cable can use a completely +different path on the real net. VDE supports also multiple concurrent VDE cables +between a pair of VDE-switches during the hand-off. This eliminates when possible +hich-ups of communications due to hand-offs. -HOWTO and command syntax: +HOWTO and basic command syntax (for a complete explanation RTM): vde-switch [ -unix control-socket ] [ -tap tuntap-device ] [ -hub ] [-daemon] -This command creates a VDE switch. +This command creates a VDE switch. -unix control-socket -The control socket is the socket used for local processes to create a new connection. The default value is /tmp/vde.ctl. User-mode-linux default value is /tmp/uml.ctl, so if you want to use vde with UML you can: (1) use "-unix /tmp/uml.ctl" for vde-switch (2) use -"eth0=daemon,,/tmp/vde.ctl" for UML + The control socket is the socket used for local processes to create a new + connection. The default value is /tmp/vde.ctl. + User-mode-linux default value is /tmp/uml.ctl, so if you want to use vde + with UML you can: (1) use "-unix /tmp/uml.ctl" for vde-switch (2) use + "eth0=daemon,,/tmp/vde.ctl" for UML -tap tuntap-device -the vde-switch is connected to the specified tap interface. Ususally it is reserved for root as /dev/net/tun is not writable. (It is dangerous to have /dev/net/tun writable by ordinary users). + the vde-switch is connected to the specified tap interface. + Ususally it is reserved for root as /dev/net/tun is not writable. + (It is dangerous to have /dev/net/tun writable by ordinary users). -hub -the vde-switch works as a hub (all packets are broadcast on all interfaces. + the vde-switch works as a hub (all packets are broadcast on all interfaces. -daemon -the switch works as a daemon: it runs in background, it uses syslog for error management. - -vde-plug [-g num] [socketname] -A vde-cable is composed by two vde-plug and a "cable". A vde-plug connects its standard input and output to a switch. -socketname is the control-socket of the switch the plug must be connected to (default value /tmp/vde.ctl). --g num (num > 0, num < 256) is a group number. Cables without a group number are independent cables, cables with the same group number represent several path for the same destination. Packet reaching a switch on a cable are never forwarded on another cable of the same group. + the switch works as a daemon: it runs in background, it uses syslog + for error management. + +vde-plug [-p port] [socketname] +A vde-cable is composed by two vde-plug and a "cable". A vde-plug connects its +standard input and output to a switch. +socketname is the control-socket of the switch the plug must be connected to +(default value /tmp/vde.ctl). +-p port. To use a specific port of the switch. The first available port is +assaigned when not specified. It is possibl eto connect several cables to the +same prot: Cables connected to the same port represent several path +for the same destination. dpipe cmd1 [arg1] = cmd2 [arg2] -it is the double pipe command (it is here just becouse it is not provided by shells). -cmd1 and cmd2 are executed, the stdout of cmd1 if pipe connected to the stdin of cmd2 and viceversa. (the symbol = is intended as a pair of communication pipes between the two processes. +it is the double pipe command (it is here just becouse it is not provided by +shells). +cmd1 and cmd2 are executed, the stdout of cmd1 if pipe connected to the stdin of +cmd2 and viceversa. (the symbol = is intended as a pair of communication pipes +between the two processes. HOW TO: - (1) SETUP A DAEMON: (as root) -# vde_switch -tap tap0 -daemon +# vde_switch -tap tap0 -mod 777 -daemon # ifconfig tap0 192.168.0.254 -# chmod 777 /tmp/vde.ctl - -if you want to have routing to the Internet you can use standard routing commands on the host machine e.g.: +if you want to have routing to the Internet you can use standard routing +commands on the host machine e.g.: # echo "1" > /proc/sys/net/ipv4/ip_forward # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE for ipv6 -# echo "1" > /proc/sys/net/ipv6/conf/eth0/forwarding +# echo "1" > /proc/sys/net/ipv6/conf/eth0/forwarding # radvd radvd must be configured to broadcast the correct prefix for the tap0 subnet - + ----- example of /etc/radvd.conf file interface tap0 { - AdvSendAdvert on; - MaxRtrAdvInterval 120; + AdvSendAdvert on; + MaxRtrAdvInterval 120; #put here your prefix. - prefix 1111:2222:3333:4444::/64 - { - AdvOnLink on; - AdvAutonomous on; - AdvRouterAddr on; - - }; + prefix 1111:2222:3333:4444::/64 + { + AdvOnLink on; + AdvAutonomous on; + AdvRouterAddr on; + + }; }; ------ end of example @@ -89,68 +119,81 @@ interface tap0 % dpipe vde_plug = vde_plug /tmp/my.ctl (or -% dpipe vde_plug /tmp/my.ctl = vde_plug +% dpipe vde_plug /tmp/my.ctl = vde_plug ) -connects the vde_switch with ctl socket /tmp/vde.ctl with the other using /tmp/my.ctl. +connects the vde_switch with ctl socket /tmp/vde.ctl with the other using +/tmp/my.ctl. - (3) CONNECT TWO REMOTE SWITCHES TOGETHER -You need a tool to interconnect stdin stdout of two remote processes. e.g. +You need a tool to interconnect stdin stdout of two remote processes. +e.g. % dpipe vde_plug /tmp/my.ctl = ssh remote_machine vde_plug -connects the vde_switch with ctl socket /tmp/vde.ctl on the remote_machine with the local switch using /tmp/my.ctl. +connects the vde_switch with ctl socket /tmp/vde.ctl on the remote_machine +with the local switch using /tmp/my.ctl. -It is possible to use other tools in place of ssh like netcat.In this latter case the communication is not secure. +It is possible to use other tools in place of ssh like netcat. +In this latter case the communication is not secure. - (4) CREATION OF TUNNELS. (it needs kernel support for policy routing) -Setup two daemon as described in (1). In this example 192.168.0.1 is the tap0 address on the server side. +Setup two daemon as described in (1). +In this example 192.168.0.1 is the tap0 address on the server side. Route the traffic to the Internet on the tunnel server side. On the tunnel client side: -- in the example 100.200.201.202 is the IP address on eth0 -and 100.200.201.254 is the default gateway. - -- create a specific rule for the eth0 routing - ip rule add from 100.200.201.202 table eth0-table -(please note that eth0-table must be listed in /etc/iproute2/rt_tables) - - ip route del default via 100.200.201.254 - ip route add default via 100.200.201.254 table eth0-table - -the previous default route will be the def. route just for the packets originated with the eth0 inteface address. - -- connect the two vde-switch together: - dpipe vde-plug = ssh -b 100.200.201.202 server-machine vde-plug - -- setup an appropriate IP address for tap0 interface (or get it by dhcp if set up on server side). (e.g. 1 92.168.0.10) - -- use tap0 as the default interface: - ip route add default via 192.168.0.1 + - in the example 100.200.201.202 is the IP address on eth0 + and 100.200.201.254 is the default gateway. + - create a specific rule for the eth0 routing + ip rule add from 100.200.201.202 table eth0-table + (please note that eth0-table must be listed in /etc/iproute2/rt_tables) + ip route del default via 100.200.201.254 + ip route add default via 100.200.201.254 table eth0-table + the previous default route will be the def. route just for the + packets originated with the eth0 inteface address. + - connect the two vde-switch together: + dpipe vde-plug = ssh -b 100.200.201.202 server-machine vde-plug + - setup an appropriate IP address for tap0 interface (or get it by dhcp + if set up on server side). (e.g. 192.168.0.10) + - use tap0 as the default interface: + ip route add default via 192.168.0.1 - (5) SUPPORT FOR MOBILITY Create a tunnel like in 4 using a group number on the vde-cable: -dpipe vde-plug -g 1 = ssh -b 100.200.201.202 server-machine vde-plug -g 1 + dpipe vde-plug -g 1 = ssh -b 100.200.201.202 server-machine vde-plug -g 1 Create a second tunnel (say on ppp0 addr. 100.100.101.102 gateway 100.100.101.254) -# ip rule add from 100.100.101.102 table ppp0-table -# ip route add default via 100.100.101.254 table ppp0-table + # ip rule add from 100.100.101.102 table ppp0-table + # ip route add default via 100.100.101.254 table ppp0-table Connect the a second cable using the same group number: -# dpipe vde-plug -g 1 = ssh -b 100.100.101.102 server-machine vde-plug -g 1 - + # dpipe vde-plug -g 1 = ssh -b 100.100.101.102 server-machine vde-plug -g 1 Disconnect the first cable (kill the processes of the first cable) -All the traffic get rerouted on the new vde-cable (thus to another path on the rel network. Connections in place are unaffected by the change. Several cables of the same group can be in place during the handoff phase but note that this ends up in duplicated packets that can slow down the communication. + All the traffic get rerouted on the new vde-cable (thus to another path + on the rel network. Connections in place are unaffected by the change. + Several cables of the same group can be in place during the handoff phase + but note that this ends up in duplicated packets that can slow down + the communication. -Please note also that the vde-switches do not manage (yet) the minimum spanning tree protocol thus a loop in the topology can lead to inconsistent MAC forward tables and to network saturation. +Please note also that the vde-switches do not manage (yet) the minimum spanning +tree protocol thus a loop in the topology can lead to inconsistent MAC forward +tables and to network saturation. -Copyright 2003/2004 Renzo Davoli +Copyright 2003/2004/2005/2006/2011 Renzo Davoli +This product includes software developed by Danny Gasparovski and Fabrice +Ballard (slirp support). Acknowlegments: -Thanks to Marco Giordani, Leonardo Macchia for their useful help for debugging. Imported code by Danny Gasparovsky, Fabrice Ballard. Code organization, bugfixes, autotool support Mattia Belletti. +Thanks to Marco Giordani, Leonardo Macchia for their useful help for debugging. +Imported code by Danny Gasparovsky, Fabrice Ballard. +Thanks to Giuseppe Della Bianca for many bug reports, and +patch proposals. +Thanks to Daniel P. Barrange for several patches +and the management of group ownership. +Code organization, bugfixes, autotool support Mattia Belletti. -This page found at http://www.blogin.it/vde.htm diff --git a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst index b37a1f0..05c906b 100644 --- a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst +++ b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.lst @@ -3,12 +3,12 @@ || Package: ./vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz || ++======================================== -drwxr-xr-x root/root 0 2020-05-22 21:57 ./ -drwxr-xr-x root/root 0 2020-05-22 21:57 install/ --rw-r--r-- root/root 808 2020-05-22 21:57 install/slack-desc -drwxr-xr-x root/root 0 2020-05-22 21:57 usr/ -drwxr-xr-x root/root 0 2020-05-22 21:57 usr/doc/ -drwxr-xr-x root/root 0 2020-05-22 21:57 usr/doc/vde-2.3.2/ +drwxr-xr-x root/root 0 2021-05-08 12:26 ./ +drwxr-xr-x root/root 0 2021-05-08 12:26 install/ +-rw-r--r-- root/root 808 2021-05-08 12:26 install/slack-desc +drwxr-xr-x root/root 0 2021-05-08 12:26 usr/ +drwxr-xr-x root/root 0 2021-05-08 12:26 usr/doc/ +drwxr-xr-x root/root 0 2021-05-08 12:26 usr/doc/vde-2.3.2/ -rw-r--r-- root/root 18003 2011-11-23 10:41 usr/doc/vde-2.3.2/COPYING -rw-r--r-- root/root 26436 2011-11-23 10:41 usr/doc/vde-2.3.2/COPYING.libvdeplug -rw-r--r-- root/root 3012 2011-11-23 10:41 usr/doc/vde-2.3.2/COPYING.slirpvde @@ -20,6 +20,7 @@ drwxr-xr-x root/root 0 2020-05-22 21:57 usr/doc/vde-2.3.2/ -rw-r--r-- root/root 726 2011-11-23 10:41 usr/doc/vde-2.3.2/README.qemu -rw-r--r-- root/root 208 2011-11-23 10:41 usr/doc/vde-2.3.2/README.slirpvde -rw-r--r-- root/root 933 2011-11-23 10:41 usr/doc/vde-2.3.2/README.vde_over_ns +-rw-r--r-- root/root 11325 2005-02-09 10:16 usr/doc/vde-2.3.2/Using_VDE_with_QEMU_HOWTO.txt -rw-r--r-- root/root 44824 2011-11-23 10:41 usr/doc/vde-2.3.2/VirtualBox-3.1.6_OSE_VDE.patch drwxr-xr-x root/root 0 2011-11-23 10:42 usr/doc/vde-2.3.2/bochs/ -rw-r--r-- root/root 329 2011-11-23 10:41 usr/doc/vde-2.3.2/bochs/eth.cc.diff @@ -30,16 +31,16 @@ drwxr-xr-x root/root 0 2011-11-23 10:42 usr/doc/vde-2.3.2/libvdemgmt/ -rw-r--r-- root/root 27 2011-11-23 10:41 usr/doc/vde-2.3.2/libvdemgmt/closemachine.rc -rw-r--r-- root/root 56 2011-11-23 10:41 usr/doc/vde-2.3.2/libvdemgmt/openmachine.rc -rw-r--r-- root/root 415 2011-11-23 10:41 usr/doc/vde-2.3.2/libvdemgmt/sendcmd.rc --rw-r--r-- root/root 6345 2011-12-06 08:18 usr/doc/vde-2.3.2/rc.vdenetwork --rw-r--r-- root/root 8427 2020-05-22 21:57 usr/doc/vde-2.3.2/vde.SlackBuild +-rw-r--r-- root/root 6345 2020-05-23 23:52 usr/doc/vde-2.3.2/rc.vdenetwork +-rw-r--r-- root/root 8427 2021-05-08 12:26 usr/doc/vde-2.3.2/vde.SlackBuild -rw-r--r-- root/root 1397 2011-11-23 10:41 usr/doc/vde-2.3.2/vde_autolink-HOWTO -rw-r--r-- root/root 233 2011-11-23 10:41 usr/doc/vde-2.3.2/vdecmd -rw-r--r-- root/root 11065 2011-11-23 10:41 usr/doc/vde-2.3.2/vdeqemu-HOWTO -drwxr-xr-x root/root 0 2020-05-22 21:57 usr/include/ --rw-r--r-- root/root 1775 2020-05-22 21:57 usr/include/libvdehist.h --rw-r--r-- root/root 4615 2020-05-22 21:57 usr/include/libvdemgmt.h --rw-r--r-- root/root 2665 2020-05-22 21:57 usr/include/libvdeplug.h --rw-r--r-- root/root 5634 2020-05-22 21:57 usr/include/libvdeplug_dyn.h --rw-r--r-- root/root 4220 2020-05-22 21:57 usr/include/libvdesnmp.h +drwxr-xr-x root/root 0 2021-05-08 12:26 usr/include/ +-rw-r--r-- root/root 1775 2021-05-08 12:26 usr/include/libvdehist.h +-rw-r--r-- root/root 4615 2021-05-08 12:26 usr/include/libvdemgmt.h +-rw-r--r-- root/root 2665 2021-05-08 12:26 usr/include/libvdeplug.h +-rw-r--r-- root/root 5634 2021-05-08 12:26 usr/include/libvdeplug_dyn.h +-rw-r--r-- root/root 4220 2021-05-08 12:26 usr/include/libvdesnmp.h diff --git a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta index 52f9565..7b5a2c8 100644 --- a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta +++ b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.meta @@ -1,8 +1,8 @@ PACKAGE NAME: vde-2.3.2-x86_64-1lem.tgz PACKAGE MIRROR: https://mirror.slackware.mx/libremex/slackbuilds PACKAGE LOCATION: ./vde/pkg64/current -PACKAGE SIZE (compressed): 52 K -PACKAGE SIZE (uncompressed): 200 K +PACKAGE SIZE (compressed): 56 K +PACKAGE SIZE (uncompressed): 210 K PACKAGE DESCRIPTION: vde: vde (virtual distributed ethernet) vde: diff --git a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc index cb4f701..d185c4d 100644 --- a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc +++ b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.asc @@ -1,17 +1,17 @@ -----BEGIN PGP SIGNATURE----- -iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAl7J8z0ZHGd6YW11ZGlv -QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZVxMeD/96kJvAxNz8WLIbAj2MGPgj -1tgY8QbSVVeHeUEuYB9sV1vw1d/RIO8c6mbVmO8VINbbiyhtOD0KNPCuk7wUuIin -lSK5OUtqv4/vhdJnItQNHrTa0pikPvhwMmg16+HWEPVj98tQ5fWS6n/i3M3klZU2 -mMNqMvLSjBRXJJSZKvFrTsVNxGJO++Mdg4vRjiUt3Zw4MGdoLzkt3a8iV0Bqvlgo -szTR06wRDn7iqZVT15/92LbU0F+quQyxVCHX/ImlBDJbvzKOifO5/pZqKc+25bEz -KYPia6lejt2oBKMeNVLUgELhwCOq6gkj7nWFTxV9PhCQ35CsJZUd4/yR8iJeLwSb -qthPWACJIrMdvRWbs6gl0A8QP7LUY3VOfVcTpRkHmzrNgH0Ya4dSHhGxl96zQ500 -kLSF59v1avjC+XgIUfwuhmzalG+ex2lSsds1bcum37PhQf9HNque+7taRZnf82F6 -IN7S7Vl5EsYRDxyaLQ5eB+Rw+qRhDbkgYJFrMinzQjeexloODIG6vSCyQuJ+kQxL -0nw1aqIq97/y8aozodj5UI4sbyEOq3sJxspewLU+QjYWbeqVM9mFdzxp4hVaQSCj -hHCchFTTIGCTwm/2wtKR3naMtia13+fG/4LGEpe8Rf4WC3jaj6LuNShHKRip+dW4 -Vx+oefh/coLYW6oNMhBAiQ== -=2XkN +iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv +QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV/qzD/wKleGt9t9nZiolas5NEcfV +pkwSMO6szX/ComGDgifQiWzJszapoZUhNSPMj90CmDMmXOSuc3ctwDF0RMt4w3hZ ++NJodiwOUMyf6XrozP/AqTYIjamF+gXEVCDh0hKYabUtZPWsFwBu6gV/duvwid+F +MZ0nLyEDJo8s+P+q0eR1axM0xSqCLlHoBjLes+5FHzOm2fh+kgwLgB21qOhNY0G6 +VZ4pAzUeYqHKwUvHkHygRqAgqjJjA6p5BNc2zl5ABi/bS76lSZJJ+Lt3NihSKhDC +iO7kkvEnzKy4dvpt9Sj9NtN6JT/NmxA5Kn1KlMt1G2ipl2f0Xbvb1gnUuNSmIeNb +mklijtWVhMprr6+2PrYd2YwXXzvrqP4G1ZCjvTJ9RA63c9+RckDeIo7dfrOr8IAp +CxngU791hktfX094uwW/iHODO6YMJoBsLDQJlxH1BioJC8KidxRgeuyST96CsfeX +m+zP/avgN4h6O+C/gLT6jXGL17r4TF/VGjZb3EiLQGGxIzuhdU2JmFnA3lwu+ZPY +zOVHrENHCqlrynRckzAm0Ui1k7VOoeuL7RDRcAepJFxHcOvUeluvkU/Sx/8aigIF +Z6sXZkXKV5dW7mXbYepKCM1/P+LzDEmK3ecfO8VMrC2PGmEdtMgpt8N39XA3fWhl +eRRta1mUpyFG0x9KBEDC0Q== +=bYb2 -----END PGP SIGNATURE----- diff --git a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 index c03244a..0c0f08b 100644 --- a/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 +++ b/vde/pkg64/current/vde-2.3.2-x86_64-1lem.tgz.md5 @@ -1 +1 @@ -2c98ce79f27034eb98785cfed4e59bdc vde-2.3.2-x86_64-1lem.tgz +ce63d20ab5959b6a98d30d37f448bbab vde-2.3.2-x86_64-1lem.tgz