Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Operating Systems Ubuntu Linux

Ubuntu Linux 19.10 'Eoan Ermine' Beta Available For Download (betanews.com) 41

Canonical today released the official beta for the upcoming Ubuntu Linux 19.10. Code-named "Eoan Ermine," it features Linux kernel 5.3. From a report: There are several great desktop environments from which to choose too, such as KDE Plasma, Budgie, and the default GNOME. Ubuntu 19.10 is not a long term support (LTS) version, sadly, so support for the stable release will only be a mere 9 months. "The Ubuntu team is pleased to announce the beta pre-release of the Ubuntu 19.10 Desktop, Server, and Cloud products. Codenamed "Eoan Ermine," 19.10 continues Ubuntu's proud tradition of integrating the latest and greatest open source technologies into a high-quality, easy-to-use Linux distribution. The team has been hard at work through this cycle, introducing new features and fixing bugs," says Adam Conrad, Software Engineer, Canonical.
This discussion has been archived. No new comments can be posted.

Ubuntu Linux 19.10 'Eoan Ermine' Beta Available For Download

Comments Filter:
  • by iggymanz ( 596061 ) on Friday September 27, 2019 @02:52PM (#59243866)

    nope, LTS is the way to fly for anything important, upgrade every 2 years to the next LTS if you want "fresher"

  • by ArchieBunker ( 132337 ) on Friday September 27, 2019 @03:00PM (#59243904)

    Incorporate the new systemd home directory service? You know the new feature that makes /home rely on boot services that may or may not have infinite timeouts. Oh and it will also automount containers of questionable origin? How about a network config GUI that doesn't apply settings until you toggle the interface on and off? Because Ubuntu 18 sure does that.

    • Re:Does it (Score:5, Informative)

      by slack_justyb ( 862874 ) on Friday September 27, 2019 @03:28PM (#59244044)

      I mean all the following in the nicest way possible. Just some heads up on your points.

      Incorporate the new systemd home directory service? You know the new feature that makes /home rely on boot services that may or may not have infinite timeouts.

      That hasn't even been developed. Here's Slashdot's article [slashdot.org] that you more than likely are thinking stating that it's something that's still being worked out.

      Oh and it will also automount containers of questionable origin?

      Very likely you are thinking about this. [slashdot.org] To which, if you aren't sure about the snap, then perhaps you shouldn't install it? Additionally, you can just as easily remove and not automatically load snaps if you so wish. That's all configurable things. [ubuntu.com]

      How about a network config GUI that doesn't apply settings until you toggle the interface on and off?

      Did you file a bug report on that?

      • He doesn't want to configure anything - he just wants to complain about defaults and is too lazy (let's not assume stupid) to read the man pages to customize his OS. Windows users who regedit things to their liking take more personal responsibility.

        • The defaults should be minimalist. If you want features then enable them. Not enable 1000 pieces of garbage that change config locations every release.

          • The defaults should be minimalist.

            No. Defaults should functionally suit the masses, not the minimalists. I expect my system to work when I boot it up the first time, not for me to have to enable every bloody thing individually.

          • Why? So you can complain it doesn't do out of the box without additional steps the things you are complaining it does without taking additional steps? People like you just want to complain no matter how ridiculous the complaint.
    • It includes systemd-kernel, systemd-efi and systemd-cpu_microcode.

      In the next version, you will need to get systemd-think installed at your local systemd-church!

      Hail Poettering!

      _ _ _ _
      [INB4 #triggererd #360nojoke]

    • You know the new feature that makes /home rely on boot services that may or may not have infinite timeouts.

      Wow you know how something works and that it doesn't have any fail over mechanisms before it has even been developed. Quick I need 6 numbers between 1 and 42... I'm about to head to the newsagent.

      No doubt you're also on the systemd-jounald bad bandwagon because you can't figure out how to turn on traditional text based logging.

  • by vanyel ( 28049 )

    How do you even pronounce that?

    • by rossdee ( 243626 )

      You don't pronounce anything in Linux

  • by BAReFO0t ( 6240524 ) on Friday September 27, 2019 @03:27PM (#59244038)

    It's a systemd/Linux distribution. Just like Android/Linux, calling that Linux, is (deliberately?) misleading.

    People will blame annoyances they only knew from Apple or Microsoft, on Linux. People will think "that" is what Linux is. Because that seems to be your intention.

    If you're happy with it, you can do whatever you want in your crazy world, of course. But you are actively and deliberately ruining one of the best tools we have in our lives. Meaning you are harming our lives!

    You don't get to ruin *our* thing!
    To try it some more ... and that's gonna end badly for you.

    • by slack_justyb ( 862874 ) on Friday September 27, 2019 @03:59PM (#59244196)

      It's a systemd/Linux distribution. Just like Android/Linux, calling that Linux, is (deliberately?) misleading.

      I didn't know RMS was on here. Okay, Linux is a kernel. Anything with the Linux kernel is running, Linux. Now you may have conjured some imaginary litmus test where that's not the case, but anything that runs the Linux kernel is indeed Linux. The level of access you have to that kernel, the UI you use to interface with the kernel, the system up system that kernel calls after finish loading, and so on are irrelevant to the fact that asm calls to the kernel under one have the same effects of asm calls to kernel services as the other (unless of course you didn't compile that particular service). Yeah, you may not have your standard sysv startup, but I can write a module for the kernel on Slackware, which I use, and that same module will work just as fine under Ubuntu or Android. Will it work for BSD? Maybe, but maybe not, depends on how close to the kernel's POSIX interface I stick to, but then that's a different kernel.

      I get it, we all have our favorite toolchain, init, GUI, chroot or FreeBSD jail or whatever else, vi or emacs, and what not. But saying that whatever it is we like is the definition of something and things we don't like fall outside the definition of the word is just tribalism. Ubuntu is a Linux Distribution, just like Slackware is a Linux distribution. They both have Linux as the kernel. I mean we can get pedantic about it just like RMS was/is about it, and start adding all kinds of "slashes" to the title so it'll make us feel happy, but at the end of the day, it's running a Linux kernel.

      People will blame annoyances they only knew from Apple or Microsoft, on Linux. People will think "that" is what Linux is. Because that seems to be your intention.

      Perhaps, people blame things and come to ill-formed conclusions everyday about all kinds of things. That's sounds a lot more like a fundamental flaw of humans not investigating what they are getting themselves into and less a naming convention issue. If someone jumps into a Linux distro without reading the documentation, what makes you think they're going to look up the difference between SystemD/GNU/X11/KDE/clang/CMake/nano/Linux versus sysvinit/GNU/Wayland/XFCE/vim/gcc/make/Linux? I mean shoot, I think I'm underselling the number slashes I could potentially put on a name considering all the flame wars that break out daily. If they aren't going to read up on the distro, why is making a complex name going to solve anything?

      You don't get to ruin *our* thing!

      Ah! So the tribalism was spot on here. It's not your thing anymore than it is my thing, or Linus' things, or RMS' thing. That's not what open source is. It's open, it's open to whomever wants to have it. If you don't agree with what someone does with it, that's on you. You're fine to be angry about whatever direction whatever takes, but let's be absolutely clear on one major thing. This thing, isn't yours by whatever definition "your" you want to take. You need to understand that first before you begin to address anything else wrong with your mentality. Whoever you think "our" means, you're wrong. This belongs to no one group of anyone, it belongs to everyone to do as they see fit with.

    • Comment removed based on user account deletion
    • People will blame annoyances they only knew from Apple or Microsoft, on Linux.

      Oh I can't wait to blame things like "It just works" on Linux. Because god knows Linux is currently known as that psycho complicated hacker OS.

    • Why do you have systemd in "your" Linux distribution if you can't understand it. You probably shouldn't have incorporated it into "your" Linux distribution.
  • Definition of eoan

    "of or relating to the dawn or the east"

    Yeah, I'd never heard of it either, but now we all know a word we didn't before.

Real Users know your home telephone number.

Working...