Slashdot Mirror


Debian GNU/Linux 9 'Stretch' Installer Gets GNU Screen, Linux Kernel 4.7 Support (softpedia.com)

"Debian developer Cyril Brulebois was pleased to announce this past weekend the release and immediate availability of the eighth Alpha development snapshot of the Debian GNU/Linux 9 'Stretch' installer," reports Softpedia. An anonymous reader quotes their article: It's been four long months since Alpha 7 of Debian GNU/Linux 9 "Stretch" hit the testing channels back in July, but the wait was worth it as the Alpha 8 release adds a huge number of changes, starting with initial support for the GNU Screen terminal multiplexer and lots of debootstrap fixes, which now defaults to merged-/usr.

"debootstrap now defaults to merged-/usr, that is with /bin, /sbin, /lib* being symlinks to their counterpart in /usr (more details on: https://lists.debian.org/debian-devel/2016/09/msg00269.html)," wrote Cyril Brulebois in the mailing list announcement, where it states that default debootstrap mirror was switched to deb.debian.org.

58 comments

  1. EditorDavid, do you even edit? by Anonymous Coward · · Score: 1, Insightful

    Seems like EditorDavid isn't actually a real editor in any sense of the word. You see, a real editor would have taken one look at this submission and said, "What a minute... these 3 disconnected paragraphs don't make it clear what 'Stretch' is or why an 8th alpha release is special enough to warrant a post on Slashdot. This was clearly written by someone who may or may not understand the subject well, but doesn't know how to accurately and concisely communicate that knowledge to others. This isn't fit to post."

  2. Still poisoned by systemd? by Anonymous Coward · · Score: 0

    Thanks but no.

    1. Re:Still poisoned by systemd? by myowntrueself · · Score: 2

      Thanks but no.

      The question should be; is systemd still optional? Because Debian 8 works fine without it.

      --
      In the free world the media isn't government run; the government is media run.
    2. Re: Still poisoned by systemd? by Anonymous Coward · · Score: 0

      Good to know.
      Pity the newsworthy of this is not "Debian Stretch gets rid of systemd"

    3. Re:Still poisoned by systemd? by Anonymous Coward · · Score: 2, Insightful

      Not strictly true, it works with an alternative init, but system D is still everywhere else. The state of maintenance of the alternative inits is far from good and systemd-shim is being abandoned.

      It's systemd/debian now, get over it. Accept it or see it as damage

    4. Re: Still poisoned by systemd? by Anonymous Coward · · Score: 0

      You voted for Trump didn't you?

  3. Seriously by ArchieBunker · · Score: 0

    Why am I interested in alpha build software? In the alpha stages you're lucky it even boots. They now support "screen"? Gee I've been using that for over two decades now. What next, color framebuffer and gopher support?

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
    1. Re:Seriously by Anonymous Coward · · Score: 0

      I hear they may skip gopher completely and do gopher+

    2. Re:Seriously by Anonymous Coward · · Score: 1

      This is not about including screen as one of the packages you can install. It's about making it available during network installs[1].

      https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819988
      https://lists.debian.org/debian-boot/2016/04/msg00308.html

    3. Re:Seriously by ArchieBunker · · Score: 0

      The ability to use a text based window manager during a network install? Exactly zero people will use that, along with this mess of an OS.

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
    4. Re:Seriously by Anonymous Coward · · Score: 0

      Because it's so Alpha. The females will all come begging. Derp Derp Derp :P

    5. Re:Seriously by Anonymous Coward · · Score: 0

      Maybe you should show an interest because if you don't spot it at the alpha stages they, who every they are, might fork your entire distro and deliver a completely different os by the time you adopt it as stable. Again.

    6. Re: Seriously by Anonymous Coward · · Score: 0

      Surely being able to open five or six sessions on a box with no network and most of /usr still missing is excellent news? Especially when you consider Linux has never had virtual consoles or anything.

    7. Re:Seriously by Cramer · · Score: 1

      For people who use linux for Real Work(tm), this has been wanted for years. Run an install on headless (serial or network only) hardware and see how much you like the single terminal screen interface. You can't see any logs. You cannot get to a shell to do things outside ("in spite of") the installer. (without exiting the installer)

    8. Re: Seriously by Cramer · · Score: 1

      Right. Because no one ever accesses a system via the network or a serial port. God help you if you want to install through one of those ugly interfaces.

      (read: systems exist that don't have a gfx console. I have a room full of hardware that doesn't have video chips of any kind. Most of the hardware Sun/Oracle makes has no gfx console.)

  4. All linked in /usr ? by psergiu · · Score: 5, Informative

    All binary & lib dirs linked in /usr ?
    That's incredibly STUPID
    Don't they know why /usr existed in the 1st place ?

    Story time:

    Back in the days when today's grumpy old beardy Unix Admins were young PFYs, the Unix operating system and it's ilk were gaining more and more libraries and utilities.
    Unfortunately the hard drives at the time were very small so / was running out of space. Thus a new hard-drive was mounted at /usr, and all the binaries and libraries not needed to boot the system into multiuser were moved from /bin, /sbin & /lib into /usr/bin, /usr/sbin & /usr/lib.
    This also allowed universities to have labs full of workstations with very small and cheap HDDs and NFS-mount a single /usr (as read-only) to all of them. New software needed on all workstations ? Just put-it on the shared /usr

    So:

    Those days we have large enough storage devices for huge / partitions and cheap enough that we don't need to NFS-mount them on lots of computers.

    If you don't want to have binaries & libraries separated into / and /usr/ JUST PUT EVERYTHING IN / DAMMIT !

    --
    1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    1. Re:All linked in /usr ? by lordlod · · Score: 4, Informative

      All binary & lib dirs linked in /usr ? That's incredibly STUPID Don't they know why /usr existed in the 1st place ?

      Story time: [...]

      Of course they know why /usr existed in the first place, the article references two discussions about the merits and downsides of such a move. To me the critical argument is that the original use case you cited of late mounting /usr to a networked filesystem is already broken, mostly by udev, and fixing it is not realistic or worthwhile.

      As for shifting everything to root, I agree reflexively but there are advantages to having /usr, high on the list is the fact that people expect it and that it is the approach that Fedora takes. A move like that would impose considerable work on the entire ecosystem without any clear benefit.

      The Bottom Line though is this is a change to the default. Debian does and will continue in the future to support both arrangements. So long as people see advantages in having a separated /bin and /usr/bin and configure their systems that way they will continue to exist as a configurable option.

    2. Re:All linked in /usr ? by Anonymous Coward · · Score: 1

      The analogies reasonably extend to usage on SSD + HDD systems...

    3. Re:All linked in /usr ? by Anonymous Coward · · Score: 5, Insightful

      Of course they know why /usr existed in the first place, the article references two discussions about the merits and downsides of such a move. To me the critical argument is that the original use case you cited of late mounting /usr to a networked filesystem is already broken, mostly by udev, and fixing it is not realistic or worthwhile.

      I'm not sure that they remember why the path existed in the first place. I remember the unnecessary joining of /usr/local and /usr/X11R6. I am pretty sure they also forgot that the 'S' in sbin stands for static und not superuser.

      Regardless of this it is a bad design decision to change a well thought out file system layout because someone misplaced their files (Hello udev, hello systemd). That would have been far easier changes with less repercussions and kept the system more flexible.

    4. Re:All linked in /usr ? by Anonymous Coward · · Score: 2, Interesting

      The analogies reasonably extend to usage on SSD + HDD systems...

      Or server systems that boot from usb stick.

    5. Re:All linked in /usr ? by cerberusss · · Score: 2, Informative

      All binary & lib dirs linked in /usr ?
      That's incredibly STUPID
      Don't they know why /usr existed in the 1st place ?

      If you had read the fffffine article, you'd seen the link to an article that condenses the pros and cons: https://lwn.net/Articles/67007...
      Of course they know why /usr existed in the first place.

      Basically what it comes down to, is that only embedded systems want that separation. And everyone acknowledges that: "The discussion thus eventually turned toward whether or not Debian would risk losing a significant number of embedded users by not addressing their specific concerns. That question remains open to debate, given its speculative nature."

      In the end, it seems the advantages of one /usr directory outweighted the advantages and tradition of separate /usr, /sbin and /lib directories.

      --
      8 of 13 people found this answer helpful. Did you?
    6. Re:All linked in /usr ? by Anonymous Coward · · Score: 2, Interesting

      Seems the people behind udev break previous utility through weak design resulting in shifts in policy to compensate. They do this repeatedly with all the code they write. They final move is to co-opt all main distros as the only way to enforce policy.

      It should not be necessary to fix this. The design should be better to begin with. That might not be realistic but it would have been worthwhile.

    7. Re:All linked in /usr ? by Anonymous Coward · · Score: 1

      Debian is committed to migrate to a full redhat derivative status. Each move to adopt redhat standards allows those who object to bluster, leave.or fold. So far there has been no push back against the process that has had any appreciable change to the direction taken by the distro.

    8. Re:All linked in /usr ? by drinkypoo · · Score: 1

      If you don't want to have binaries & libraries separated into / and /usr/ JUST PUT EVERYTHING IN / DAMMIT !

      Things still puke if / fills up. That's why we have /usr and /var today. Keep them. They're good.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:All linked in /usr ? by waveclaw · · Score: 2

      I am pretty sure they also forgot that the 'S' in sbin stands for static und not superuser.

      I beg to differ: http://www.linfo.org/sbin.html

      These file in /sbin were system binaries. That is why /sbin directories are usually not on the default path for users.

      Now, /usr/sbin, that one is confusing unless you know the sorrid history of /usr as a shared NFS mount. Files in /bin and /sbin may be statically linked or not even on real UNIX. For boot-time on Linux like Debian, static linking is for stuff in your initrd, rescue images or really really badly written software (*cough* Zabbix *cough*).

      The changes directly impact two groups. Power users are going to need to know about /bin, /sbin, /usr, etc. as they are going to mess with their system directly. Package Maintainers are going to have another thing to pull hair out over when converting the raw sewage seeping out of poor developers into functional shipping things to end-users.

      Until this impacts regular users or Joe X Windows who runs SteamOS it's like the mechanic changing the brand of shocks in your car. Someone who knows better will be using the correct tools to do the correct thing. Or everyone will hang them out to dry when your transmission drops out of the car on the highway.

      --

      "You cannot have a General Will unless you have shared experiences. You cannot be fair to people you don't know."
    10. Re:All linked in /usr ? by Anonymous Coward · · Score: 0

      Which spec introduced the sbin folders? I can't find it in SysV or POSIX.

    11. Re:All linked in /usr ? by Anonymous Coward · · Score: 0

      An even better solution: static linking.

    12. Re: All linked in /usr ? by Anonymous Coward · · Score: 0

      Debian will not lose any significant users over this, because anyone who has any sense and uses Linux to Get Things Done already left quite some time ago.

    13. Re: All linked in /usr ? by cerberusss · · Score: 1

      Debian will not lose any significant users over this, because anyone who has any sense and uses Linux to Get Things Done already left quite some time ago.

      Really? I love Debian. Rock solid, I install it on all my servers.

      --
      8 of 13 people found this answer helpful. Did you?
    14. Re:All linked in /usr ? by hitmark · · Score: 1

      The "all in /usr" comes out of the containerized web monkeys that is running the userspace Linux show these days...

      What they do is they boot the "node" (aka computer) via a compressed boot image (initramfs), and then once that has set thing up, they just remount / read only to a SAN backend.

      Hell, systemd is basically built around this being the expected way. This to the point that said boot image needs to get dbus up before handing things over to systemd loaded from /. Systemd will then use that for its early stuff before killing the boot image dbus, and starting a new one from /.

      Observe how all of this is cooked up by the trifecta of Gnome, Freedesktop and Fedora, with most of the devs involved being on Red Hat payroll. Linux above the kernel has long since stopped being a community project, and become an extended arm of Red Hat.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
  5. screen? by Anonymous Coward · · Score: 0

    screen? meh. tmux is better

    1. Re:screen? by Anonymous Coward · · Score: 1

      Yeah i'll happily take a pass on screen. BTW the binary is setuid root and the source is chaotic. What was that a standard recipe for, again?

      This is why NetBSD now has tmux in base and no more screen, BTW.

    2. Re:screen? by Phil+Hands · · Score: 2

      tmux is bigger from what I remember (if you include all the libraries it pulls in that are not already present in Debian Installer).

      Also, screen gives you the ability to talk to serial ports, which might be quite useful for embedded use, which is one of the primary use-cases for this (since that is a time where you're talking to the installer over a serial/ssh connection and therefore don't have access to multiple virtual terminals)

      If you're already a user of such software, and prefer tmux (as I do too), then using screen for d-i means you can simply type Ctrl-A, rather than needing to escape Ctrl-B to deal with nested tmuxs.

      --

      Debian: GNU/Linux done the Linux way
    3. Re:screen? by Anonymous Coward · · Score: 0

      Oh no, some utility on the signed livecd that doesn't have any listening daemon and you're gonna use for less than 30 minutes might be insecure!
      captcha: idiocy

    4. Re:screen? by Cramer · · Score: 1

      Actually, it's setGid (group), so it can mess with utmp. If you don't care about it fucking with utmp, then run it as a normal user. It hasn't needed root for a long time.

      (not that anyone cares, but I've run screen on solaris as a normal user for decades. Installed in $HOME/bin even)

  6. Just ... screen? by aglider · · Score: 1

    Do all the news headlines about Debian boil down to ... screen?
    Do they know abut byobu and tmux?

    --
    Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
    1. Re:Just ... screen? by fph+il+quozientatore · · Score: 1

      It's Debian - they'll enter Stable in 2027.

      --
      My first program:

      Hell Segmentation fault

    2. Re:Just ... screen? by Anonymous Coward · · Score: 0

      Do all the news headlines about Debian boil down to ... screen?

      Do they know abut byobu and tmux?

      This is about using screen during a network install[1]. Personally, I would have preferred tmux, but it's still cool.

      tmux and byobu are both in debian main.

      https://lists.debian.org/debian-boot/2016/04/msg00308.html

    3. Re:Just ... screen? by Anonymous Coward · · Score: 0

      It's Debian, their Testing is more stable than others Stable.

    4. Re:Just ... screen? by gustygolf · · Score: 3, Informative

      Thanks, I was wondering what GNU Screen was doing in an installer ... except that your post doesn't actually really illuminate the situation at all.

      Anyway, I followed your links for a bit and here's (some) description of it : https://lists.debian.org/debia...

      I have a new idea on d-i/network-console: multi-console support (screen/tmux).

      For d-i on normal PC, we can simply press alt-F2 to get a console
      almost anytime during install, but it's not easy for current
      network-console if there's no serial console.
      So I'm wondering whether it's possible to add screen/tmux support.

      Yeah, it's not worth much, but now I can actually see the use ...

      --
      "Slow Down Cowboy! It's been 58 minutes since you last successfully posted a comment" -- slashdot, driving users away.
    5. Re:Just ... screen? by squiggleslash · · Score: 1

      It's also hard to believe that's true. screen has been around for decades, and is one of the most useful command line management tools out there. Is Debian seriously only getting it now, or did someone interpret a decision to adopt a more recent version as "Debian is going to get screen for the first time!"?

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:Just ... screen? by Anonymous Coward · · Score: 1

      It's been in Debian for ages. It's now part of the install disk image.

  7. Dayum by rrohbeck · · Score: 1

    One week after I installed with debootstrap because the old kernel and installer didn't work for me. It was a pain in the ass.

  8. Isn't the 4.7.x Kernel End-of-Life ? by kjhambrick · · Score: 1

    - Bump Linux kernel version from 4.6.0-1 to 4.7.0-1.

    I understand that this is simply the installer, but the 4.7.x Kernel recently went EoL ...

    https://www.kernel.org/.

    -- kjh

    1. Re:Isn't the 4.7.x Kernel End-of-Life ? by F.Ultra · · Score: 1

      EOL from upstream yes, Debian will maintain it perfectly well themselves.

  9. While maybe on BSDs... by Anonymous Coward · · Score: 0

    Having seperate /usr and /var on linux has been broken for DECADES. While you can manually add them if you are using the installer, most distros by default just install to a single / partition and call it a day. I personally stopped seperating them almost 2 decades ago because linux distros were bloating up so rapidly that accurately determining how big each partition should be was a lesson in futility. Just when you thought you had them sized right, oops! new app needs 10x the space in /var as you expected. Oh no, new datafiles for y app go in /usr/share. Oh no, gnu is now installed info files as mandatory and they take up 5x as much space as the manpages!

    As dumb as it is often considered, Windows having the primary drive unseperated often makes sense for systems that don't have resizable partitions/filesystems and the irregular bloating of system packages, user installed apps under /home, and data/logfiles under /var all come to the conclusion that for non-tuned systems, seperated filesystems is often less beneficial that it should be, unless you have far more disk space than you would ever use.

    Having said that, even FreeBSD doubled or tripled its / filesystem require back in the 4.x era. It went from a 128 meg min to a 256 meg min and caused all sorts of problems for me getting it to fit while upgrading to 4.7 or 4.8 maybe it was.

    1. Re:While maybe on BSDs... by drinkypoo · · Score: 1

      These days you can use LVM and grow filesystems, etc etc. So yeah, that's annoying, I agree. But it's not a show-stopper.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:While maybe on BSDs... by Anonymous Coward · · Score: 0

      For my latest linux desktop installation I went with a 20 GB / and 10 GB /home instead of a lone 20GB / partition. Wow, I'm not running out of space anymore!
      But my swap is too small and when it runs out I have to hit the reset button (I'm glad to still have one). Alright, I've added the missing second swap in the fstab so maybe I'll survive next time.
      And very likely, the computer will still hang on start up if any of the hard drives is missing, even though I could not care less. Windows boots if the C: drive is there but the D: and E: drives are missing. How come it's linux that is trying to protect me against myself, even though I didn't ask it anything :-).

      I wanted to rant about the /etc/udev/rules.d directory, but it doesn't list my network card there anymore. Now some systemd thing manages it I'm sure, I have no idea if some data is stored somewhere. Not sure if the old "feature" has been removed, by which I mean if you change your network card, then you can't access the network anymore.

    3. Re:While maybe on BSDs... by Cramer · · Score: 1

      I agree. On a PC, with the idiotic 4 partition layout, multiple partitions never made much sense. Even when distro's wanted to be all SunOS-like with 18 partitions, I always selected the "put everything in root" option -- if it had one, or went around it's back to do it anyway. (I've actually been doing that to Solaris installs for decades, too. And it does know how big those partitions need to be.)

      The largest issue with linux is the lack of any codified standard on what goes where. Even if there were, nobody would follow it. So yes, you never could know how big /, /usr, /var, /opt, /usr/local, /home, ... needed to be. The relatively recent insane solution to that has been LVM and dynamically sizing filesystems. (aka. a makeshift ZFS) Except no linux filesystem is designed for that. And thin provisioned virtual filesystems are the surest path to colossal ruin.

  10. Simple solution to this. by Anonymous Coward · · Score: 0

    It is time to fork any distros people consider worth saving and excise both systemd and these questionable not well thought out new changes from the forked linux ecosystem.

    There are plenty of 'niche' distros already taking this stance, especially the musl based ones. It is time we the techies give up the old distros to the unwashed masses and focus our energies on distros that actually make sense in the real world. That way when the next dot com crash happens from underengineered garbage causing a catastrophic failure in the networked ecosystem, we can swoop back in with alternatives that actually do what they are supposed to in a stable and understandable fashion and bring up the infrastructure again in a manner that seems miraculous to people who thought that layering on complexity would make them look smarter and more needed, rather than understanding that some complexity may be required, but only as much as can't be engineered out.

  11. how about a choice of init system by FudRucker · · Score: 1

    instead of forcing all debian users to systemD, include the option to choose which init system to use during the install of the operating system? that would be nice to have an init agnostic Linux distro,

    --
    Politics is Treachery, Religion is Brainwashing
  12. More incompatibility by Anonymous Coward · · Score: 0

    vendor lock-in for shell scripts. There will be an idiot that hard codes /usr for all the binaries like /usr/dash and so on just to mess with everyone.

    I wish they'd rename linux. It's not a unix clone anymore.

  13. Devuan: a fork of Debian without systemd. by Artemis3 · · Score: 1

    Yes, its called Devuan.

    "Devuan GNU+Linux is a fork of Debian without systemd."

    --
    Artix
    Your Linux, your init.
  14. Wow! by Anonymous Coward · · Score: 0

    This is the most exciting news I've ever read.