3 ms·

Which is exactly the point. Enterprise deploys windows machines because there are established tools and mechanisms to manage them. If you want more deployments

Which is exactly the point. Enterprise deploys windows machines because there are established tools and mechanisms to manage them. If you want more deployments of linux laptops, you need ...(see the first few slides).

jacquesm 7y ago
Google managed to do what RedHat failed at: to distribute Linux en masse for device usage. They also replaced the whole userland with either Android or ChromeOS, and they managed to do all that without breaking Linux for the rest of us. If RedHat wanted to they could simply rename it RhOS or something like that and leave the rest of Linux alone. Now we are getting this false-flag enterprise borne push to replace all of the Linux userland with something that I could have very much done without all in an attempt to let RedHat try once more to go for that elusive enterprise desktop market that they have so far failed to attract.
- db48x 7y ago
  There's a reason they call it "Redhat Enterprise Linux" and not just "Linux", and there's no reason you have to use it. Besides, any complaint about LDAP is a red herring here: he mentioned LDAP not because he wants to force you to use it, but because of the way people sometimes use LDAP to allocate UIDs across many systems. He wants to entirely eliminate the need for that allocation to happen, whether you use LDAP or not.
  - jacquesm 7y ago
    If RedHat would keep their code to themselves that would be great news. Unfortunately everybody and their brother can't stop themselves from tripping over their own feet to adopt whatever RH cooks up. Mind you, I'm all for less fragmentation in the Linux space, I'm just not for having that dictated by the likes of RH just because of their tendency to optimize for their own intended use cases and their never ending dreams of being allowed to play on the enterprise desktop.
    - db48x 7y ago
      Redhat certainly didn't force systemd on anybody. People liked it enough that they started using it in their distros too.
    - jraph 7y ago
      I don't use a Red Hat distribution, but I am pretty happy that their technology is used on the distributions I use. Maybe they are optimizing things for their own use cases, but they definitely work for me. And this presentation on this new management of home directories sounds like good news for me. Problems I have noticed are being solved now. Frankly, thanks to Red Hat for making my laptop and my servers work. I have a sound management that works and is nice to use, an init system that I can understand and use (just a few lines to write in a file to add a custom service) and makes my computers boot fast, a log that is readable, network management that is dead simple to use (and that can easily be disabled to restore the former behavior), a network discovery service that just works and makes printing (among other things) easier and probably other things. Those things are not perfect but nothing is. So how do we do? There will always be some people happy with some change and other, not happy with it.
      - jacquesm 7y ago
        > a network discovery service that just works and makes printing (among other things) easier and probably other things. Those were solved problems long ago. And then we did them all over again leading to the mess we have today.
        jraph 7y ago
        I don't agree. First there was, and there still is, CUPS for printing. Then Avahi came, and basically allowed your network printer to show up in the printing dialog without doing anything. Still printing using CUPS, but discoverable without configuration thanks to Avahi. Net gain for the user. I can't actually see a drawback here. Now say I have a machine called serv on the network I want to ssh to. I just need to type ssh serv.local and it will work. I don't need to set up a fixed IP address anymore, nor remember it. I want to play a sound on another device in the network? It's a drag and drop, thanks to Avahi and PulseAudio. I want to make a new network service usable by other computers in my domestic network? I'll just register to Avahi and boom, it's usable without configuration everywhere. No need to reinvent a service discovery wheel. I have not actually done that but I'm sure it's a relatively easy thing to do. And it just works. It's there without me installing or configuring anything. To my knowledge, you don't have those features without Avahi on GNU/Linux. And Avahi is yet another example of something you can easily uninstall if you don't like it. And this is compatible with Apple machines thanks to Lennart reusing an existing protocol. If anything, I miss it on Android.

jacquesm 7y ago

Google managed to do what RedHat failed at: to distribute Linux en masse for device usage. They also replaced the whole userland with either Android or ChromeOS, and they managed to do all that without breaking Linux for the rest of us. If RedHat wanted to they could simply rename it RhOS or something like that and leave the rest of Linux alone. Now we are getting this false-flag enterprise borne push to replace all of the Linux userland with something that I could have very much done without all in an attempt to let RedHat try once more to go for that elusive enterprise desktop market that they have so far failed to attract.

db48x 7y ago
There's a reason they call it "Redhat Enterprise Linux" and not just "Linux", and there's no reason you have to use it. Besides, any complaint about LDAP is a red herring here: he mentioned LDAP not because he wants to force you to use it, but because of the way people sometimes use LDAP to allocate UIDs across many systems. He wants to entirely eliminate the need for that allocation to happen, whether you use LDAP or not.
- jacquesm 7y ago
  If RedHat would keep their code to themselves that would be great news. Unfortunately everybody and their brother can't stop themselves from tripping over their own feet to adopt whatever RH cooks up. Mind you, I'm all for less fragmentation in the Linux space, I'm just not for having that dictated by the likes of RH just because of their tendency to optimize for their own intended use cases and their never ending dreams of being allowed to play on the enterprise desktop.
  - db48x 7y ago
    Redhat certainly didn't force systemd on anybody. People liked it enough that they started using it in their distros too.
  - jraph 7y ago
    I don't use a Red Hat distribution, but I am pretty happy that their technology is used on the distributions I use. Maybe they are optimizing things for their own use cases, but they definitely work for me. And this presentation on this new management of home directories sounds like good news for me. Problems I have noticed are being solved now. Frankly, thanks to Red Hat for making my laptop and my servers work. I have a sound management that works and is nice to use, an init system that I can understand and use (just a few lines to write in a file to add a custom service) and makes my computers boot fast, a log that is readable, network management that is dead simple to use (and that can easily be disabled to restore the former behavior), a network discovery service that just works and makes printing (among other things) easier and probably other things. Those things are not perfect but nothing is. So how do we do? There will always be some people happy with some change and other, not happy with it.
    - jacquesm 7y ago
      > a network discovery service that just works and makes printing (among other things) easier and probably other things. Those were solved problems long ago. And then we did them all over again leading to the mess we have today.
      - jraph 7y ago
        I don't agree. First there was, and there still is, CUPS for printing. Then Avahi came, and basically allowed your network printer to show up in the printing dialog without doing anything. Still printing using CUPS, but discoverable without configuration thanks to Avahi. Net gain for the user. I can't actually see a drawback here. Now say I have a machine called serv on the network I want to ssh to. I just need to type ssh serv.local and it will work. I don't need to set up a fixed IP address anymore, nor remember it. I want to play a sound on another device in the network? It's a drag and drop, thanks to Avahi and PulseAudio. I want to make a new network service usable by other computers in my domestic network? I'll just register to Avahi and boom, it's usable without configuration everywhere. No need to reinvent a service discovery wheel. I have not actually done that but I'm sure it's a relatively easy thing to do. And it just works. It's there without me installing or configuring anything. To my knowledge, you don't have those features without Avahi on GNU/Linux. And Avahi is yet another example of something you can easily uninstall if you don't like it. And this is compatible with Apple machines thanks to Lennart reusing an existing protocol. If anything, I miss it on Android.