Announcement

Collapse
No announcement yet.

Alpine Linux 3.10 Brings Support For Intel's IWD, Better Arm Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Raka555
    replied
    There is a certain beauty to the simplicity that Alpine brings. It lets you do what you need to without getting in your way.

    Leave a comment:


  • Raka555
    replied
    Originally posted by caligula View Post
    The last time I tried to suggest Alpine for containers at work, the 1st problem was not having systemd/dbus so couldn't log in with machinectl login. The 2nd problem was the lack of glibc. OpenJDK 8 was there, great. But.. had to install glibc wrappers to run a small Java/SWT program that assumed SWT JNI libraries that happened to depend on glibc.
    One of Alpine's core components is musl libc, now wanting glibc specific behavior tells you that you picked the wrong tool.

    Alpine is a fresh take on many things that other distro's are doing wrong (IMO). If you want a distro that behaves like distro xyz, you should be using distro xyz and not try to bend Alpine to behave like distro xyz ...

    Alpine is my favorite distro atm.
    It is impossible to run some of the mainstream broken software on top of Alpine
    Last edited by Raka555; 19 June 2019, 06:12 PM.

    Leave a comment:


  • aronwolf
    replied
    Originally posted by caligula View Post
    The last time I tried to suggest Alpine for containers at work, the 1st problem was not having systemd/dbus so couldn't log in with machinectl login. The 2nd problem was the lack of glibc. OpenJDK 8 was there, great. But.. had to install glibc wrappers to run a small Java/SWT program that assumed SWT JNI libraries that happened to depend on glibc.
    When you use containers, like docker, the most recommended is to run one process per container. In the case you want to run more than one, there exist some bash script on the homepage of docker. Of course, a container tool can be used with systemd but this comes with many inconveniences:

    * scaling: it is more difficult to create more containers on demand. Eg. you have mysql (or whatever) and a web application. Then, how can create on demand more containers without causing a lot of problems (when they are both in the same container)?
    *restarting: when you use containers, then it is really easy to restart a container if one fails (or auto deploys it to other servers).
    Last edited by aronwolf; 19 June 2019, 04:48 PM.

    Leave a comment:


  • caligula
    replied
    The last time I tried to suggest Alpine for containers at work, the 1st problem was not having systemd/dbus so couldn't log in with machinectl login. The 2nd problem was the lack of glibc. OpenJDK 8 was there, great. But.. had to install glibc wrappers to run a small Java/SWT program that assumed SWT JNI libraries that happened to depend on glibc.

    Leave a comment:


  • Alpine Linux 3.10 Brings Support For Intel's IWD, Better Arm Support

    Phoronix: Alpine Linux 3.10 Brings Support For Intel's IWD, Better Arm Support

    Alpine Linux 3.10 is out today as the newest feature release for this lightweight, security-minded Linux distribution built atop Musl libc and Busybox while catering being quite popular in the container crowd...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Working...
X