8 ms·

So, how to do it right? What are THE right steps to crosscheck stuff available from local vendor (to make eventual warranty claims easier) with linux compatibil

by rini17 5y ago

So, how to do it right? What are THE right steps to crosscheck stuff available from local vendor (to make eventual warranty claims easier) with linux compatibility? I am actually using linux desktop 20 years and still it feels like groping in the dark every time i buy some peripheral. Plus I can confirm the regressions mentioned in the article caused by relentless churn in the kernel are very real. Oh and userspace churn too. I have whole system from gcc4.9/Qt4 era saved to chroot into whenever I need some "old" software. For lay user such hoops are impossible.

mschuster91 5y ago
> I have whole system from gcc4.9/Qt4 era saved to chroot into whenever I need some "old" software. For lay user such hoops are impossible. A simple "docker run -it -v /:/mnt debian/eol:$CODENAME bash" should give you a working Debian chroot without any hassle - you can go as far back as Debian potato from 2000 per https://hub.docker.com/r/debian/eol/ https://hub.docker.com/r/debian/eol/. In theory according to a SO post (https://askubuntu.com/a/1161647 https://askubuntu.com/a/1161647) you should even be able to get GUI applications working inside a Docker container.
- rini17 5y ago
  You're missing the point, confirming the generally dismissive or even ignorant attitude. What if there's no deb package? How to make home directory accessible? The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland.
  - mschuster91 5y ago
    > You're missing the point, confirming the generally dismissive or even ignorant attitude. I get the issue if you're still dealing with chroots. I hated this with a passion, too - but using Docker is a real breeze in comparison. > What if there's no deb package? A Debian archive docker image behaves just like an ordinary Debian install would - they are fancy chroots. Install the dependencies, run the usual "./configure && make && make install" dance, that's it. > How to make home directory accessible? Add a "-v /home:/home" in the invocation. > The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland. Agree with you on that one, with one exception... systemd unit files are so much easier to deal with than init.d shellscripts.
    - rini17 5y ago
      I don't trust systemd and docker, sorry. No idea if it's my bad luck or what, every time I tried out such a complex thing with "easy" interface, I ran into some insidious bug.

by rini17 5y ago

mschuster91 5y ago

> I have whole system from gcc4.9/Qt4 era saved to chroot into whenever I need some "old" software. For lay user such hoops are impossible. A simple "docker run -it -v /:/mnt debian/eol:$CODENAME bash" should give you a working Debian chroot without any hassle - you can go as far back as Debian potato from 2000 per https://hub.docker.com/r/debian/eol/ https://hub.docker.com/r/debian/eol/. In theory according to a SO post (https://askubuntu.com/a/1161647 https://askubuntu.com/a/1161647) you should even be able to get GUI applications working inside a Docker container.

rini17 5y ago
You're missing the point, confirming the generally dismissive or even ignorant attitude. What if there's no deb package? How to make home directory accessible? The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland.
- mschuster91 5y ago
  > You're missing the point, confirming the generally dismissive or even ignorant attitude. I get the issue if you're still dealing with chroots. I hated this with a passion, too - but using Docker is a real breeze in comparison. > What if there's no deb package? A Debian archive docker image behaves just like an ordinary Debian install would - they are fancy chroots. Install the dependencies, run the usual "./configure && make && make install" dance, that's it. > How to make home directory accessible? Add a "-v /home:/home" in the invocation. > The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland. Agree with you on that one, with one exception... systemd unit files are so much easier to deal with than init.d shellscripts.
  - rini17 5y ago
    I don't trust systemd and docker, sorry. No idea if it's my bad luck or what, every time I tried out such a complex thing with "easy" interface, I ran into some insidious bug.