On Thu, Sep 14, 2017 at 11:04 AM, Nikola M <[email protected]> wrote:
> On 09/13/17 10:01 PM, Peter Tribble wrote: > >> In my OpenSolaris t-shirt collection, I have one with the slogan: >> >> "Innovation happens everywhere" >> > > So you want us to dream? :) > Yeah. But dream bigger. Not just "I wish illumos did this thing that [insert competitor here] does", but "I wish illumos did this thing that nobody can do". > - Would like to have playing sound just don't suck on illumos, kracking, > stopping, pausing, really don't care if it about boomer or pulseaudio or > vlc or driver or firefox, or inability for user processes to have higher > priority - just make the sound work without such awful problems. That would > really be a breakthrough for me. > > - Would also like per-zone I/O scheduling to be a standard across the > illumos distribution so the whole system doesn't get choked if something > is dumping cores while something else is playing audio or trying to do > something else in the real time. > I'm not sure the solution helps here. The problem with I/O scheduling is that it's often one or two steps removed from the application that's causing it, so you end up addressing the symptom rather than the underlying problem. > And yes, run all processes in the zones, together with X/GUI support , I > think Opensolaris already had that before, with the focus on different > security realms. > So the fate of trusted is pretty much open. I'm not sure whether it even works. And the old trusted desktop stuff, which is what you're thinking of, is essentially gone. But using zones for isolation like Qubes OS is something I've played with a little bit. Overall, the standard uses for zones only scratch the surface of what the underlying technology is capable of, so there's an opportunity there to use zones in far more interesting ways. > - illumos on ARM for mobile, coupled with hardware manufacturers, having > linux-android zones. Utilizing binary compatibility (with ABI stability) > for illumos/ARM applications for mobile, across devices, not relying on > Java VM, working faster. > Coupling devices with "bunch of zones" or "zones groups" on the cloud > providers, representing that same device and possibly also running the same > apps in the cloud. With block-level replications from the device to the > cloud (with dataset encryption in the cloud). > ABI stability and presence on the mobile market could be the real > incentive for the new young people to join in. > > - Make systems run something out of the box , tailored per-use case. > Systems usually do nothing after install. Make them have AI-like behavior > out of the box , trying to do something useful while just sitting there > doing nothing after fresh install. With some questions here and there about > bandwidth, metered/non metered connection, desired actions. > So bundling up appliances? I'm sure there was an OpenSolaris project along those lines, but can't recall the details off-hand. I did have some thoughts on that for AWS instances - basically you stick in some metadata (tags) for the instance, it queries the tags (there's a neat API for that), installs the appropriate package(s) and configures itself. For regular systems it's a shame that the IPS-based installers don't have much in the way of customization of the install. > - After finally implementing OpenCL, AMD graphics drivers, have GPU > processing power shared across zones and applications with speed > throttling. Have also PCI-e-Passthrough for VMs and distributed OpenCL > framework running at the same time. > -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ------------------------------------------ illumos-discuss Archives: https://illumos.topicbox.com/groups/discuss/discussions/T83f198c8597cf8e3-Mcb3ed7b891d485f752edfbeb Powered by Topicbox: https://topicbox.com
