search for: hackware

I just bought two new Linksys WRT54G routers. Sveasoft has loaded Linux on this router and included a bunch of Linux tools, one of which is Bandwidth Management. The QoS aspect of this is supposed to be much more granular than the previous solution (Wonder Shaper). I have not been able to find any suggestions for how to impliment QoS (Bandwidth Management) using the web interface of Alchemy.

...is apparently lost on those who did not live through the pre-distribution days. During that time we had to gather up the dependencies ourselves, trying to get the correct versions, hoping that the software compiled and worked with the other dependencies, and hope we did not install malware and hackware. And quite often it was a futile attempt to gather together software dependencies of any size. Those who lived through that time remember it as the dark-ages of long ago, never to be seen again. Neil Nelson On 4/4/20 11:48 AM, Mehdi AMINI via llvm-dev wrote: > > > On Thu, Apr 2, 2020...

...urce is apparently lost on those who did not live through the pre-distribution days. During that time we had to gather up the dependencies ourselves, trying to get the correct versions, hoping that the software compiled and worked with the other dependencies, and hope we did not install malware and hackware. And quite often it was a futile attempt to gather together software dependencies of any size. Those who lived through that time remember it as the dark-ages of long ago, never to be seen again. Been there, done that... (actually suffered from that). I claim this is just not the same situation he...

...urce is apparently lost on those who did not live through the pre-distribution days. During that time we had to gather up the dependencies ourselves, trying to get the correct versions, hoping that the software compiled and worked with the other dependencies, and hope we did not install malware and hackware. And quite often it was a futile attempt to gather together software dependencies of any size. Those who lived through that time remember it as the dark-ages of long ago, never to be seen again. Been there, done that... (actually suffered from that). I claim this is just not the same situation he...

...did not live through the pre-distribution >> days. During that time we had to gather up the dependencies ourselves, >> trying to get the correct versions, hoping that the software compiled and >> worked with the other dependencies, and hope we did not install malware and >> hackware. And quite often it was a futile attempt to gather together >> software dependencies of any size. >> >> Those who lived through that time remember it as the dark-ages of long >> ago, never to be seen again. >> >> Been there, done that... (actually suffered from t...

...urce is apparently lost on those who did not live through the pre-distribution days. During that time we had to gather up the dependencies ourselves, trying to get the correct versions, hoping that the software compiled and worked with the other dependencies, and hope we did not install malware and hackware. And quite often it was a futile attempt to gather together software dependencies of any size. > > Those who lived through that time remember it as the dark-ages of long ago, never to be seen again. > > Been there, done that... (actually suffered from that). > > > > I...

I’m in favor of all this. Thanks for volunteering! I’m happy to help out in whatever way. Some things it might be worth figuring out for future upgrades: * If we want to limit ourselves to CMake versions supported by LTS releases of distros, which distros should we consider, and how far back should we go (i.e. is it just the latest LTS or the last two LTS versions)? * For platforms like Ubuntu