now lots of packages/services are in the iso , its size is too large ,for daily work ,it is not useful . if these package could be installed through additional group ,I think that is better . telegraf itself take about 200MB … it is too much for a router .
Im not sure its “too large”.
Arista EOS for comparision is about 1.1Gbyte in size when you download that from their site.
What can be argued is if the additional binaries and libraries (which today are included by default) might be a security threat even if the feature isnt actively enabled by the VyOS config.
As I recall it last year VyOS stated they worked on some kind of “addon” support where VPP would be the first such addon to “sideload” after install. But I think the main purpose for that addon system was to be able to release commercial addons and not necessary to make some of todays binaries/libraries “optional”.
Technically since VyOS is debian based you can uninstall (along with any dependencies which no longer will be needed) using apt. However the ISO will remain of its original size and the “deleted” files will only be so through the persistent directory (they will basically be marked deleted and not visible from the CLI).
hmm , both openwrt and mikrotik are small , anyway ,like debian ,it also provide base system or slim system to install . now ,lots of features can be provided by containers , this give customers/users more options . telegraf as an example , too large ,i’m not sure how many users use it .
“addon” or “optional” packages should be good and keep the base system slim/clean .
Well FloppyFW was even smaller (1.44MB floppy but was extended to (reformat into) 1.68MB floppy to be able to squeeze in some additional packages such as tc (trafficshaping) etc)…
But the thing if you want to compare lets say Mikrotik with VyOS is that Mikrotik is also highly limited (even if it can do alot).
Mikrotik now even struggle with having the WIFI addonpackage for devices with WIFI since the onboard storage is limited to 16MB or so. As in when you upgrade you risk to lose WIFI connectivity which is a bummer when you are a WISP (Wireless ISP) where the uplink goes through WIFI or similar.
But their need to keep things small is due to limited onboard storage - something that doesnt really apply to a VyOS installation where if you want to buy a drive today the smallest out there are normally in the size of 120GB (cheapest SSD around here according to https://prisjakt.nu).
Which gives if the VyOS image is 500MB or 700MB its more like “meh” even if I would also prefer a smaller size (which is why I spent some time on commits to optimize the squashfs compression and other fixes to shrink the imagesize along with also having a suggestion to not include the kernel twice in the image where the later was postponed since the change wouldnt be backward compatible):
The key point is not compared with openwrt/mikrotik , vyos is based on debian , I just hope there is an option to provide base system like debian , that is enough for most case . Telegraf is not key service/feature, but take about 200M ,it doesn’t make sense .
It is not mikrotik and there is no “base system”
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.