It doesn’t matter. What matters is tgat there’s now rose-storage optiobal package which neatly packs various network file sharing protocols (SMB, NFS, iSCSI, etc.) and it’s a great opportunity to declare that if somebody wants to use RB as NAS server (including SMB), then this is entirely optional feature. They might even rename rose-storage to “nas” to make clear to everybody what it was (WTH does rose stand for?). Yeah, it’ll break plenty of configs, many users will blindly upgrade without reading changelogs. But it would be a relatively clean cut. And a few (tens? hundreds?) of kB more free space for all those who never used SMB would be very welcome. It might be enough to allow to install e.g. zerotier package?
It’s a great idea to rename to “nas”! I love roses, like well Guns’n’Roses, rose flowers, rose perfume and so on… but how it is related to SMB I really don’t understand!
I am able to achieve a maximum of 464K free HDD space with a clean netinstall and no configuration except for the default scripts. When I stripped the configuration (advanced QoS removal), I’m able to live with 350-400K free HDD. But anything close to 1MB is absolutely unattainable. It’s a pity that when reaching 0 KB of free space on the HDD, the router becomes unbootable and a netinstall is required.
the rose-storage package does not only offer the “nas” function, but also the “client” function. In fact that is the only part
of it that I am using. With rose-storage you can access a NAS share from within the router, i.e. you can mount a folder within
the router Files section onto a share on your NAS. (that “NAS” of course could be another MikroTik router)
It does not only work with SMB, but also with NFS, iSCSI, and NVMe/TCP.
NAS (like QNAP, Synology) can mount another NASes, also it can run Docker, can run Photo Gallery, Video Surveillance, remote access, of course NFS, iSCSI and so on. Anyway, “rose” is counter-intuitive naming. All in all, it’s not that important, just “rose” here, “rose” there, and finally we’ll stuck with something what nobody will understand
Yes, I ignore it, the intention here was just to show how something as simple as starting a service at the right time would avoid an error appearing at the beginning of startup.
Ah, MikroTik changelogs.
Anyway, the size is obviously not the same, probably another reason for those 120KB.
I’ve checked the changelog posted above for beta8 and there’s no mention of that. http://forum.mikrotik.com/t/v7-14beta-testing-is-released/172080/324
Not that I’m surprised by the missing information from changelogs.
It is not as simple as you think. Some of those services may be circularly dependent. E.g. a VPN may require DNS to determine the endpoint, while the user may want to run DNS over his VPN.
I simply do not use DoH, it serves no useful purpose for me.
And that’s the brutal irony: You might want to use client parts of ROSE/NAS on a 16MB device to mount an external disk. While now you’re getting SMB server parts to potentially share the 16MB flash? The “full” ROSE is only applicable on a few devices, but parts of ROSE/NAS are useful on more but it does not fit.
And a lot of users just like remove features they don’t need, yet you cannot. And good reasons to want to: less attack surface, increase available storage, less stuff in the UI, or fit “extra” packages that aren’t extra in your use cases.
*) leds - added “dark-mode” functionality for hAP ax3 and Chateau ax series devices;
How do I enjoy this for hAP-ax3? I tried with ip leds settings but there is not a “dark mode” anywhere (set all leds off option was already there before this release, but it only shutdown front leds).
My God i wonder the same, im so irritated by LEDS going nuts during night, why isnt it possible to make ALL leds(front and ones on LAN ports) go complete off?