3 ms·

Not who you asked, but here's my answer: - Webcam on MacBook Pro (some dude reverse engineered it but I packaged it into dkms .deb so I didn't have to compile

Not who you asked, but here's my answer: - Webcam on MacBook Pro (some dude reverse engineered it but I packaged it into dkms .deb so I didn't have to compile every time I updated the kernel) - vpn through company firewall (which didn't support Linux, and wasn't openvpn compatible, took absolutely ages to get it working) - getting the thing to properly sleep, wake and not chew the battery - fuck Nvidia and Lenovo (different laptop) I still prefer Linux and use it as my daily driver.

GekkePrutser 5y ago
> vpn through company firewall (which didn't support Linux, and wasn't openvpn compatible, took absolutely ages to get it working) I'm cherry picking here but in this case you're just doing your company's endpoint management job for them. This was my last job and I have also spent a lot of time packaging and scripting (for autoconfiguration, I don't like presenting the end user with technical questions if we already know the answer to). On entirely supported platforms. This kind of thing is a full time job in many companies so if you go outside of the supported path and do your own then obviously it's going to take considerable time :)
- raffraffraff 5y ago
  Yep. Palo Alto. There is very limited Linux support, but not for the authentication method we used (which did some browser-based auth that I don't quite remember)
- oblio 5y ago
  > I'm cherry picking here but in this case you're just doing your company's X job for them. This is a recurring theme with Linux, because guess what, many companies want nothing to do with desktop Linux, for better or for worse. So you'll have to do their job for them, as a side gig.
  - _abox 5y ago
    Well, or you can use the tools they give you to do your job :) I agree the focus isn't there. I was managing everything "not Windows" as an endpoint architect and it was very difficult to get other teams to consider them. Makes sense because "not Windows" was less than 1% of our userbase. So I had to really push for them to select tools like VPN and antivirus that support Linux and Mac. However we did manage. What I did see a lot was that R&D users didn't want to use the standard supported distro (which by the way I picked with their input). They complained about all the mandatory antivirus software (which was not my choice, but the security team's mandate). But really there was a very high amount of "I just want to manage everything myself" going on too. You can't have it both ways though. Either you get a managed endpoint and you have to roll with some of the decisions or you do it all yourself (and in some cases are locked out of some critical environments due to security policy) This is fine (well fine by me, but not by our security team!) but then don't complain about how hard it is to get it set up. I can see how WSL fits well into this for companies, though I prefer real Linux myself too. A lot of R&D users would be on Mac as it's a "Linuxy enough" OS with much less hurdles in a corporate environment (native MS Office available etc).

GekkePrutser 5y ago

> vpn through company firewall (which didn't support Linux, and wasn't openvpn compatible, took absolutely ages to get it working) I'm cherry picking here but in this case you're just doing your company's endpoint management job for them. This was my last job and I have also spent a lot of time packaging and scripting (for autoconfiguration, I don't like presenting the end user with technical questions if we already know the answer to). On entirely supported platforms. This kind of thing is a full time job in many companies so if you go outside of the supported path and do your own then obviously it's going to take considerable time :)

raffraffraff 5y ago
Yep. Palo Alto. There is very limited Linux support, but not for the authentication method we used (which did some browser-based auth that I don't quite remember)
oblio 5y ago
> I'm cherry picking here but in this case you're just doing your company's X job for them. This is a recurring theme with Linux, because guess what, many companies want nothing to do with desktop Linux, for better or for worse. So you'll have to do their job for them, as a side gig.
- _abox 5y ago
  Well, or you can use the tools they give you to do your job :) I agree the focus isn't there. I was managing everything "not Windows" as an endpoint architect and it was very difficult to get other teams to consider them. Makes sense because "not Windows" was less than 1% of our userbase. So I had to really push for them to select tools like VPN and antivirus that support Linux and Mac. However we did manage. What I did see a lot was that R&D users didn't want to use the standard supported distro (which by the way I picked with their input). They complained about all the mandatory antivirus software (which was not my choice, but the security team's mandate). But really there was a very high amount of "I just want to manage everything myself" going on too. You can't have it both ways though. Either you get a managed endpoint and you have to roll with some of the decisions or you do it all yourself (and in some cases are locked out of some critical environments due to security policy) This is fine (well fine by me, but not by our security team!) but then don't complain about how hard it is to get it set up. I can see how WSL fits well into this for companies, though I prefer real Linux myself too. A lot of R&D users would be on Mac as it's a "Linuxy enough" OS with much less hurdles in a corporate environment (native MS Office available etc).