Difference between revisions of "Packets status and perspective"

From vsd
Jump to navigation Jump to search
(Created page with "List of current packets (Buster): <pre> SOURCE vde2 Package: vde2 Package: vde2-cryptcab Package: libvdeplug-dev Package: libvdeplug2 Package: libvde-dev Package: libvde0 SOU...")
 
m
Line 44: Line 44:
 
Package: libexecs0
 
Package: libexecs0
 
Package: libexecs-embedded0
 
Package: libexecs-embedded0
 +
</pre>
 +
 +
List of Repositories
 +
<pre>
 +
On GitHUB (repository -> binary packet(s) + comments):
 +
cado -> cado
 +
fuse-ext2 -> fuse-ext2 (hybrid exec-library)
 +
libnlq -> libnlq, libnlq-dev
 +
libpam-net ->
 +
libslirp -> libslirp, libslirp-dev (
 +
libstropt -> libstropt, libstropt-dev (include in v2utils?)
 +
libvdestack -> libvdestack, libvdestack-dev
 +
libvolatilestream -> libvolatilestream, libvolatilestream-dev (include in v2utils?)
 +
nsutils -> DISCUSS: is it useful?
 +
purelibc -> libpurelibc, libpurelibc-dev
 +
s2argv-execs -> okay
 +
strcase -> libstrcase-dev (it is a macrolibrary. include in v2utils?)
 +
userbindmount -> userbindmount, libuserbindmount, userbindmount-dev (include in v2utils?)
 +
v2tools -> insert in v2utils?
 +
vde-2 -> vde2, vdeplug, libvdeplug2 (virtual packet?)
 +
vde_dnsutils -> vde_dnsutils (is thi
 +
vdens -> vdens
 +
vdeplug4 -> vdeplug4, libvdeplug2, libvdeplug2-dev, ....
 +
vdeplug_agno -> vdeplug_agno
 +
vdeplug_pcap -> vdeplug_pcap
 +
vdeplug_slirp -> vdeplug_slirp
 +
vdeplug_vlan -> vdeplug_vlan
 +
(??? one source package vdeplug4_plugins)
 +
vuos -> umvu, umvu-dev, ???
 +
vxvdex -> ??? there is a kernel module
 +
 +
Name collisions (AFAIK):
 +
* libvdeplug, vde_plug
 +
* vuname
 +
 
</pre>
 
</pre>

Revision as of 15:19, 16 April 2019

List of current packets (Buster):

SOURCE vde2
Package: vde2
Package: vde2-cryptcab
Package: libvdeplug-dev
Package: libvdeplug2
Package: libvde-dev
Package: libvde0

SOURCE lwipv6
Package: liblwipv6-dev (liblwipv6-2)
Package: liblwipv6-2 (libvdeplug-dev)

SOURCE vdetelweb
Package: vdetelweb (liblwipv6-dev, libvde-dev)

SOURCE purelibc
Package: libpurelibc-dev
Package: libpurelibc1

SOURCE umview
Package: umview (libvdeplug-dev, libfuse-dev, liblwipv6-dev)
Package: libumlib0
Package: libumlib-dev
Package: umview-mod-umlwip
Package: umview-mod-umdevtap
Package: umview-mod-viewfs

SOURCE fuse-umfuse-ext2
Package: umview-mod-umfuseext2 (libumlib-dev, libfuse-dev)
Package: fuseext2

SOURCE fuse-umfuse-fat
Package: umview-mod-umfusefat (libumlib-dev, libfuse-dev)
Package: fusefat

SOURCE fuse-umfuse-iso9660
Package: umview-mod-umfuseiso9660
Package: fuseiso9660

SOURCE: libexecs
Package: libexecs-dev
Package: libexecs0
Package: libexecs-embedded0

List of Repositories

On GitHUB (repository -> binary packet(s) + comments):
cado -> cado
fuse-ext2 -> fuse-ext2 (hybrid exec-library)
libnlq -> libnlq, libnlq-dev
libpam-net -> 
libslirp -> libslirp, libslirp-dev (
libstropt -> libstropt, libstropt-dev (include in v2utils?)
libvdestack -> libvdestack, libvdestack-dev
libvolatilestream -> libvolatilestream, libvolatilestream-dev (include in v2utils?)
nsutils -> DISCUSS: is it useful?
purelibc -> libpurelibc, libpurelibc-dev
s2argv-execs -> okay
strcase -> libstrcase-dev (it is a macrolibrary. include in v2utils?)
userbindmount -> userbindmount, libuserbindmount, userbindmount-dev (include in v2utils?)
v2tools -> insert in v2utils?
vde-2 -> vde2, vdeplug, libvdeplug2 (virtual packet?)
vde_dnsutils -> vde_dnsutils (is thi
vdens -> vdens
vdeplug4 -> vdeplug4, libvdeplug2, libvdeplug2-dev, .... 
vdeplug_agno -> vdeplug_agno
vdeplug_pcap -> vdeplug_pcap
vdeplug_slirp -> vdeplug_slirp
vdeplug_vlan -> vdeplug_vlan
(??? one source package vdeplug4_plugins)
vuos -> umvu, umvu-dev, ??? 
vxvdex -> ??? there is a kernel module

Name collisions (AFAIK):
* libvdeplug, vde_plug
* vuname