News for hackers. Stuff that matters.
Re:Debian Dropping the Linux Standard Base by pippy on Thursday October 08, 2015 @07:35PM (#10357135)
I've always liked the concept behind GoboLinux[1], it makes so much more sense in comparison to the legacy mainframe style file structure other linux distros use. Debian dropping LSB might pave the way for more distros adopting a more modern and sensible file structure.

1 http://www.gobolinux.org/?page=at_a_glance

Re:Debian Dropping the Linux Standard Base by JdeBP on Thursday October 08, 2015 @10:35PM (#10357816)
This is nothing new, of course. NeXTStep introduced things like ~/Apps, /LocalLibrary, and /LocalApps back in the early 1990s.

Daniel J. Bernstein, around the turn of the century, proposed a /package hierarchy (for package management without the need for conflict resolution) and a /command directory. (http://cr.yp.to/slashpackage.html) Their major problem was the idea that one had to register things with what was to most of the world just some bloke on another continent. But they had concepts like a hierarchical package naming scheme ("admin/", "mail/", &c.), self-contained build trees with versioned names, and an "index" directory full of symbolic links.

Re:Debian Dropping the Linux Standard Base by gcb0 on Thursday October 08, 2015 @11:54PM (#10358059)
the problem is exactly that. some group in an ivory tower refuses to (or can't?) move. most of posix is like that. Linux "standard" for gui stuff is still some definition from IBM to normalize DOS apps (reason why F10 open menus, copy paste with ctrl+ins, shift+ins, etc).

then people that can't work together with others (eg Jobs) does retarded things like /localLibrary which benefit nobody, not even themselves. just throw everything up. then if those folks succeed despite that, it becomes the new immutable thing to follow, like gnome is doing with following blindly apple ui specs.

edit: i never tried to contribute to any larger standard. i did develop against most of them, cursed at their anachronistic ways and coded around it praising consistency. so i am pretty sure i am part of the problem described above. I'm not saying the fine people in those ivory towers are the problem. I'm glad we have that little help for world consistency. it's just not enough.

Re:Debian Dropping the Linux Standard Base by JdeBP on Friday October 09, 2015 @08:19AM (#10359508)
You're taking received wisdom from Wikipedia, and it's wrong. Common User Access was for normalizing IBM applications, across its then hardware platforms: the PC, System/3x, and System/370. Indeed, it's most promiment PC success was 32-bit IBM OS/2, which implemented the later CUA 91 and which most definitely wasn't DOS.
Re:Debian Dropping the Linux Standard Base by gcb0 on Friday October 09, 2015 @03:38PM (#10362764)
well, whatever the actual reason, i actually (used to) consult it when writing CURSE applications only because it is the closest we have for a curses application usability standard.

where it came from originally is not much of concern. but the fact that it is the best we have, is.

Re:Debian Dropping the Linux Standard Base by spacemanmatt on Friday October 09, 2015 @09:43PM (#10364143)
It wasn't bad. I appreciate the attempt to reduce my cognitive load.
Re:Debian Dropping the Linux Standard Base by smegger001 on Friday October 09, 2015 @01:13AM (#10358302)
I do not seem to understand, so forgive my ignorance if you will but; Why do we need a /Apps directory isn't that what /bin /sbin and /usr/bin are for? And as for /LocalApps is that not what /home/$user/bin is for? this seems fairly redundant, or needless wheel reinventing?
Re:Debian Dropping the Linux Standard Base by wtallis on Friday October 09, 2015 @03:36AM (#10358634)
On NeXTSTEP and OS X, the /Apps (/Applications) directory is for self-contained application bundles that hold a GUI application and all of its dependencies that aren't part of the base OS, and they can be installed and removed by dragging and dropping that one bundle (which is a directory, but appears in the graphical file manager as a single object). There was also a distinction between locally-installed stuff and network resources which made things a little more complex but more manageable if you were actually working in an office full of NeXT boxes. OS X still has /usr and it still has pretty much the same meaning, but GUI apps live in a separate and more user-friendly domain.
Re:Debian Dropping the Linux Standard Base by pjmlp on Friday October 09, 2015 @03:46AM (#10358663)
Known on Windows world as xcopy install, due to the similar way MS-DOS software used to be bundled and everyone used xcopy instead of the pretty basic copy that didn't do recursive copies.

But sadly it doesn't present the nice object concept NeXTSTEP and OS X have.

Re:Debian Dropping the Linux Standard Base by nailer on Friday October 09, 2015 @03:07AM (#10358568)
Not advocating for one of the other, but they're not the same. /Apps is based on the application that supplied the files, /usr vs / is based on whether necessary to boot the OS, /bin vs /lib vs /share based on the file type.
Re:Debian Dropping the Linux Standard Base by BinaryIdiot on Friday October 09, 2015 @02:38AM (#10358505)
Probably just more intuitive more than anything else. Someone without prior knowledge to the operating system (or even computers in general) and things like /Apps is really obvious where as /bin and /sbin understanding is really going to depending on how much someone knows about computers.
Re:Debian Dropping the Linux Standard Base by lottin on Friday October 09, 2015 @03:27AM (#10358617)
As far as I know, /Apps is for packages that ship with their own versions of shared libraries and everything else the program needs to run; all files are installed in one directory under /Apps, instead of where they actually belong in the Unix directory structure.
Re:Debian Dropping the Linux Standard Base by rakoo on Friday October 09, 2015 @08:46AM (#10359630)
/bin and friends are for binaries only. For a full package you also want libraries, man pages, configuration files etc... Those are usually bundled as a .tar.gz which would ideally be the best way to bundle and distribute a program.
Re:Debian Dropping the Linux Standard Base by brbsix on Friday October 09, 2015 @05:55AM (#10359064)
This sounds somewhat similar to /opt (albeit more complicated), wherein programs are located in /opt/package or /opt/provider. For example, the entirety of Sublime Text is stored in /opt/sublime_text and Google programs are stored in subdirs of /opt/google.
Re:Debian Dropping the Linux Standard Base by caf on Thursday October 08, 2015 @07:58PM (#10357235)
Debian has specifically said that they will be continuing to use the FHS (Filesystem Hierarchy Standard).
Re:Debian Dropping the Linux Standard Base by wscott on Friday October 09, 2015 @05:48AM (#10359045)
Or Nix https://nixos.org/ where every package is stored by a hash of its build environment. So every version can coexist.
Re:Debian Dropping the Linux Standard Base by baldfat on Friday October 09, 2015 @07:24AM (#10359324)
I have been saying for years our Linux Package System is broken and antiquated. When we had 40 MB hard drives or no hard drives at all these systems made sense. Today we can have a system that just works like this or Gobo Linux. I have hopes that with containers that we will see some major distro switch (Looking at Arch Linux) to a non-shared everything libraries.
Re:Debian Dropping the Linux Standard Base by jordigh on Friday October 09, 2015 @11:26AM (#10360641)
The point of the FHS is not to save disk space, although that's a nice side effect. The point is to not have multiple copies of the same bug or slightly different bug across each package.
Re:Debian Dropping the Linux Standard Base by lsaferite on Friday October 09, 2015 @09:35AM (#10359861)
Well, then why have any libs if none will be shared? Why not just statically compile the application so it's a single binary?
Re:Debian Dropping the Linux Standard Base by Kristine1975 on Friday October 09, 2015 @10:43AM (#10360296)
Security updates perhaps: If e.g. OpenSSL is shared, a single security update will fix all applications using it. And a single update will most likely be out more quickly than updates to a dozen or so applications.
Re:Debian Dropping the Linux Standard Base by takeda on Friday October 09, 2015 @12:19PM (#10361105)
The thing is that the libraries are not shared, and every application has its own version of library in its application directory. So if you would want to update OpenSSL you would have to find openssl in every single application and update (or more likely wait for vendor to release new version with more recent openssl).

At that point the shared libraries are useless, they don't provide security (update in one place and have all aps using it patched), doesn't save RAM (each app loads their own version of library, instead of multiple apps sharing the same code), and you get worse performance (there's overhead for using shared libraries).

What lsaferite suggested makes sense, if the library is used only by given app, why not compile it statically? You have everything in a single file, and at least you're not losing performance by using shared objects.

Re:Debian Dropping the Linux Standard Base by baldfat on Friday October 09, 2015 @10:05AM (#10360073)
I love the idea EXCEPT for Desktop Enviroments. Does that mean any KDE/Gnome App has the whole desktop installed in each folder?

What about OpenSSH does that mean any program that uses SSH needs its own copy and then we have 12 different versions of SSH?

Its not easy but I am sure someone is smart enough to figure this stuff out. NixOS and Gobo Linux have tried.

Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:21PM (#10361124)
The scheme that Canonical seems to be playing with is that larger projects (DEs, central libs) are put into what they call frameworks.

These are packages that other packages can refer to rather than massively duplicating the content within themselves.

These frameworks will in turn be versioned, so that if package X wants framework Z, while Y wants Z+1 they can both be happy without descending into dependency hell.

Note that Gobolinux gets around this to a degree by using age old soname and symlinks. This in that ld and similar is pointed at a directory containing symlinks.

libxyz.so.1 will be pointing to whatever is the active version of libxyz, while something like libxyz.so.1.1 will be pointing to that specific lib version.

Disabling a specific lib version is done by removing the relevant symlinks.

Gobolinux provides tools for doing this, but they are basically shell scripts. And so in a pinch someone can do all that manually.

Re:Debian Dropping the Linux Standard Base by wcummings on Friday October 09, 2015 @10:40AM (#10360281)
How does a Gobo-style package management system deal w/ security updates for shared components? Do you rely on the vendor that packages them?
Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:12PM (#10361037)
I guess it will depend on the size of the distro project backing it. Gobo, by "virtue" of being a small group, can't provide a large store of pre-compiled packages. Thus one at present have to rely on compiling on ones own.

That said, once compiled a binary package can be produced by simply creating a compressed archive of the content of /Programs/app-name/app-version (an official binary package is a bit more involved to ensure compatibility with the latest released iso).

Beyond that i am not quite sure what you are asking.

Re:Debian Dropping the Linux Standard Base by motoboi on Thursday October 08, 2015 @07:54PM (#10357216)
We have a Linux distributing organizing programs in a different way: Android.

It seems to be working pretty good, actually, with compartmentalization and tight security.

Re:Debian Dropping the Linux Standard Base by alphapapa on Friday October 09, 2015 @02:52AM (#10358538)
It's funny you should say that. I've been using Android for several years after using iPhones. And I find myself wishing all the time for a phone that simply runs Debian Stable.

Tight security? Well, how about Stagefright? Cyanogen no longer supports my phone. Even when they did, it wasn't well-supported: each new release had a high chance of breaking something fundamental. Right now I'm stuck on a "milestone" release that isn't even the newest one (it's over a year old now!), because later ones all have some unacceptable problem, like GPS not working or cell data not working. I can't just install an updated browser component package, because Android is monolithic. On Debian it'd be in a package like libwebkit, and it'd be a simple "apt-get upgrade" away.

So I'm stuck with a vulnerable Android version. If I try to upgrade to fix it, I'll lose GPS or cellular data. The only way to get a fix is to buy a new phone.

Now Google is trying to push more of the components into its Google Play Service app/framework. So, great: more parts can be upgraded independently of the monolithic core. But that also means that Google can push out updates to more components without my knowledge or consent: not great. That means more instances of feeling something warm in my pocket, pulling out my phone, and finding that Google Play Services has kept my phone awake for 10 hours and my battery is at 12%.

This has happened to me on multiple occasions: one day my phone works fine. The next day it eats the battery like candy. I didn't change any settings or install any updates--Google merely decided to push out an automatic update to its APKs without my knowledge or consent, and Google Play Services constantly crashes every 5 seconds, popping up a dialog box that I have to manually dismiss. I can't even do a simple task like send an SMS or check my email, because every 5 seconds it pops up another "Unfortunately..." box. There's no practical way to roll it back, nor even to report the problem. The best I can do is find people reporting the same problem on Reddit and hope that Google gets its act together so I can actually have a usable phone again; maybe one morning I'll wake up and my phone will not be "sick" anymore. In the meantime I have a really dumb "smartphone" that keeps my leg warm.

I have had high hopes for Android, but I now consider it to be a mess, and consider Google to be a highly irresponsible steward. I don't want an iPhone, but if someone wants a reliable smartphone without nasty surprises, they are probably better served with one.

Re:Debian Dropping the Linux Standard Base by throwaway7767 on Friday October 09, 2015 @06:15AM (#10359121)
I really miss maemo, it was pretty much what you're describing. Being able to rebuild packages directly from the debian archive if I wanted some new software, or patch some system software and put it in my own APT repository, are things I really liked.

In addition to the problems you describe with google moving more core functionality into its "Google Apps" packages, it also means that running android without the google bits is getting increasingly hard. It's missing some core functionality that other non-google apps expect.

Re:Debian Dropping the Linux Standard Base by bmn_ on Friday October 09, 2015 @12:14PM (#10361063)
Get a Nemo or Sailfish device. http://enwp.org/File:Mer_and_mobile_operating_systems.svg

Public build service is https://openrepos.net/ and it already has lots of packages that you know from a normal Linux desktop and you can also host your custom stuff there. High-level package manager is packagekit or zypper.

Having a private repo is easy, too. Package format is RPM, repo format is http://createrepo.baseurl.org/

Re:Debian Dropping the Linux Standard Base by brbsix on Friday October 09, 2015 @06:36AM (#10359172)
I would also recommend using something like AOSP with a very minimal GApps install. Or bake your own ROM if you really need fine control. I even had to build a modified TWRP recovery in order to fully support my latest device. Additionally, use a firewall and Xposed with XPrivacy to tightly reign in apps. However the reality is that this is no fun, and not something you can expect the average consumer to do. It is quite unfortunate and I have similar sentiments.
Re:Debian Dropping the Linux Standard Base by qznc on Friday October 09, 2015 @02:59AM (#10358556)
You can disable automatic updates. You can remove Google Play Services.

Similar problems happen with Debian as well. E.g. hibernation breaks or WiFi stops working.

Re:Debian Dropping the Linux Standard Base by alphapapa on Friday October 09, 2015 @03:17AM (#10358595)
I never enable automatic app updates. However, Google Play Services is unaffected by this setting--it updates whenever Google wants it to, without any indication to the device owner.

Sure, I could use Android without Google Play Services. That would also mean not being able to use the vast majority of apps in the Play Store--and I don't mean games. That would mean not being able to use, e.g. Google Maps.

So to use Google Maps, I should have to give Google free rein to push updates to its software to my phone whenever it wants, including untested updates that cause breakage, crashes, and battery draining causing high temperatures?

This is what's wrong with Android.

And you can't seriously claim that such drastic breakage happens on a regular basis with Debian Stable.

Re:Debian Dropping the Linux Standard Base by tetheno on Friday October 09, 2015 @03:59AM (#10358703)
You can use AOSP and install the Google Maps apk without Google Play Services. It's a hassle though.

I would also like to have more control over what Google does in my Android phone while not losing the ability to install apps easily.

Re:Debian Dropping the Linux Standard Base by pjmlp on Friday October 09, 2015 @03:50AM (#10358673)
Actually thanks to the Android architecture, having Linux as the kernel is pretty irrelevant to most users and developers.

Given the thin APIs exposed in the NDK, Google could change it by any UNIX flavored kernel and no one would notice.

The OEMs might be a bit pissed off if they had to change the APIs, but that's all.

Re:Debian Dropping the Linux Standard Base by hiphopyo on Thursday October 08, 2015 @08:18PM (#10357305)
Doesn't Android borrow a lot of code from NetBSD and OpenBSD?
Re:Debian Dropping the Linux Standard Base by duskwuff on Thursday October 08, 2015 @09:40PM (#10357613)
Not significantly. Some parts of Bionic (Android's libc equivalent) is based on BSD equivalents, but most of userland is Android-specific.
Re:Debian Dropping the Linux Standard Base by rhabarba on Friday October 09, 2015 @01:33PM (#10361814)
Android has a few hundred unmodified OpenBSD files.
Re:Debian Dropping the Linux Standard Base by duskwuff on Friday October 09, 2015 @02:44PM (#10362413)
A few hundred files is very little in a project the size of Android. :)
Re:Debian Dropping the Linux Standard Base by pjmlp on Friday October 09, 2015 @03:51AM (#10358675)
> but most of userland is Android-specific.

Meaning Java, which makes POSIX irrelevant.

Re:Debian Dropping the Linux Standard Base by vezzy-fnord on Thursday October 08, 2015 @07:37PM (#10357143)
Don't count on it. It's probably going to be this: http://www.freedesktop.org/software/systemd/man/file-hierarc...
Re:Debian Dropping the Linux Standard Base by craftkiller on Thursday October 08, 2015 @08:30PM (#10357349)
Why is /usr/bin being adopted as the place for binaries with /bin linking to it instead of the other way around? Since they're essentially the same directory under this setup why not favor the short path?
Re:Debian Dropping the Linux Standard Base by zarvox on Thursday October 08, 2015 @08:39PM (#10357374)
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForT...

In short: because having things in /usr is equally compatible, and makes some useful things like atomically snapshotting /usr to snapshot all executables, mounting /usr readonly, etc. possible.

Re:Debian Dropping the Linux Standard Base by craftkiller on Thursday October 08, 2015 @08:54PM (#10357441)
Ah I had not considered snapshotting just /usr before. Thanks for the link, it makes a lot more sense now!
Re:Debian Dropping the Linux Standard Base by JdeBP on Friday October 09, 2015 @09:25AM (#10359795)
It's an interesting question. One part of the the answer is that the idea is for there to be a single subtree off the root where "the operating system" lives. Where MacOS 10 has /System, OS/2 has \OS2, Windows has \Windows, and Digital Research DOS has \DOS, systemd Linux has /usr.

Of course, another part is that this is an old idea, already implemented once in the commercial Unices a quarter of a century ago. They merged /bin into /usr/bin, with a symbolic link from the former to the latter.

Re:Debian Dropping the Linux Standard Base by jonhohle on Thursday October 08, 2015 @08:40PM (#10357386)
In addition, on more complex setups, `/usr` might not be mounted during certain failure modes.
Re:Debian Dropping the Linux Standard Base by marcosdumay on Thursday October 08, 2015 @09:34PM (#10357591)
It's also not available at the first moment of the boot process.

But it is this kind of stuff that they are trying to change (as usual for systemd, without fully thinking why people do it differently now).

Re:Debian Dropping the Linux Standard Base by geofft on Thursday October 08, 2015 @10:16PM (#10357744)
A lot of those designs predated initramfs. I have yet to hear of a setup where there's a good reason for not mounting /usr in the initramfs. (Though, yes, I have heard of setups where you can, it would just be a fairly involved change. It is a legitimate problem for these sysadmins to be compelled to rearchitect things, although I'd personally blame that more on the distro model where all parts of userspace are tied together than on systemd itself.)
Re:Debian Dropping the Linux Standard Base by thaumaturgy on Thursday October 08, 2015 @08:59PM (#10357469)
That looks fine for embedded systems or maybe some end-user systems, but doing that in a server context would be scary. The original filesystem hierarchy was designed so that /usr, /etc, /bin, and so on would have their own partitions and in the event that something tried to eat the filesystem, you might still be able to boot into single user mode and repair the damage. I've had to do this on a handful of different servers where /usr is boned and won't mount, but I still have enough stuff available that I can fix it.

Plus there are a handful of tools with smart option that take advantage of the multiple partition approach, like rm and rsync's --one-file-system option.

Re:Debian Dropping the Linux Standard Base by JdeBP on Thursday October 08, 2015 @09:48PM (#10357648)
Except, of course, that /etc/init and /bin/sh being on "their own partitions" is the opposite of what was actually the case in the original filesystem hierarchy. (Hint: Yes, /etc/init not /sbin/init .)
Re:Debian Dropping the Linux Standard Base by thaumaturgy on Thursday October 08, 2015 @10:18PM (#10357751)

    [root@mail /]# ls -laF /etc/init
    ls: cannot access /etc/init: No such file or directory
Sorry, I don't follow what you're saying. Or why that would make putting everything under /Programs better for that matter.
Re:Debian Dropping the Linux Standard Base by cesarb on Friday October 09, 2015 @07:27AM (#10359333)
I believe that what JdeBP is refering to is that, before /sbin existed, the binary which is now at /sbin/init used to be at /etc/init, if I recall correctly what I once read in an old FSSTND rationale.
Re:Debian Dropping the Linux Standard Base by thaumaturgy on Friday October 09, 2015 @02:41PM (#10362395)
Huh, interesting. If that's the case, it's new to me. Neat.
Re:Debian Dropping the Linux Standard Base by powera on Friday October 09, 2015 @12:26AM (#10358164)
The original filesystem hierarchy was designed when 1MB was a large amount of space.

If you want to have a separate read-only partition for system programs (and require going into single-user mode to modify that), go for it. But the rest of the /bin /etc /usr /usr/local nonsense is just because it's easier than changing to something better for most people.

Re:Debian Dropping the Linux Standard Base by thaumaturgy on Friday October 09, 2015 @02:17AM (#10358449)
Someone should've posted a polite correction instead of downvoting you. So:

The thinking behind the file system layout had nothing to do with the available disk space or having a read-only file system. It was, originally, entirely a hedge against corruption; before journaling file systems and all that jazz, if your system was hit by a power outage and it was in the middle of some operation or another it might corrupt whatever file system it was working in.

So, you would create multiple partitions and have different directories as the mount point for each partition. Say for instance that, as a cautious sysadmin, you put /sbin on its own partition. Excellent! Since /sbin rarely gets touched, if everything goes pear-shaped, the system will still boot into single user mode and you can use tools like fsck and mount, which are under the uncorrupted /sbin partition and are statically linked. If you couldn't for some reason recover the file system on a particular partition, then you might be looking at having to load, say, /etc from backups, instead of everything under /.

Over time, other software started to take advantage of multiple partition layouts to protect you from getting hurt. You could mark some partitions noexec, nosuid, or restrict operations like rm or rsync to specific partitions without having to worry about whether or not they'll crawl out of that partition and eat the world.

But that's pretty old-school now. As file systems improved and corruption was less of a problem and everybody sort of gave up caring about what options rm accepted, more and more systems just mounted everything under / so that you would be maximally boned if ever there was a filesystem problem. Progress!

OpenBSD is one of few operating systems left that has a set of recommendations for how to partition your system: http://www.openbsd.org/faq/faq4.html#Partitioning

So that's why I'm not a fan of "novel file system layouts"; the previous layout was designed and existed for some good reasons and I have a hunch that the people that are happy about novel file system layouts don't know about those reasons.

Re:Debian Dropping the Linux Standard Base by madez on Friday October 09, 2015 @06:22AM (#10359136)
Your arguments are irrelevant nowadays.

If my filesystem gets corrupted, I boot into a live cd, just like everybody does.

With btrfs and integrated parity, checksums, cow and scrubbing on the horizon filesystem reliability is only a minor thing to care about. With subvolumes we can snapshot as many things atomically as we want.

Simlicity is now what trumps your arguments overwhelmingly. The filesystem hierarchy has to be intuitive, consistent and simple, which it is currently not.

Re:Debian Dropping the Linux Standard Base by thaumaturgy on Friday October 09, 2015 @06:55AM (#10359227)
There was a major ext4 bug just earlier this year that caused data loss for some folks: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785672

Booting a LiveCD would not have fixed affected partitions.

You're not the first on HN to say in so many words that the sometimes expensive lessons I've learned over 30 years of computing are suddenly irrelevant now. I used to argue that, but I don't see much point to it anymore.

Re:Debian Dropping the Linux Standard Base by madez on Friday October 09, 2015 @07:15AM (#10359293)
One of your arguments was to put /bin and /sbin onto a seperate partition so that if something happens, it’s unlikely that /bin and /sbin are affected. In reality however, nobody cares about /bin and /sbin at all.

Another argument was more fine grained permission control. You can do that by other means, for example with subvolumes.

So, after all, possible corruptions are not alleviated by complex partition struture, or only with a bad trade-off for complexity. Instead, do backups. Easy and reliable. Everbody is happy, without many partitions.

Simplicity is crucial and it's one thing the free software ecosystem is consistently getting wrong. I see it as the major showstopper for many people to use it more intensively.

The filesystem hierarchy is just one culprit, but a fundamental one.

Take a look at at some fundamental pure mathematics lectures or books. You can immediately see that this was designed to be as easy as possible. Software must be the same.

Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:24PM (#10361153)
> If my filesystem gets corrupted, I boot into a live cd, just like everybody does.

And that is what makes someone take the road trip to the server farm at 2am because a ge-wiz dev thought the exact same and never considered a "rescue" mode with network capability.

Re:Debian Dropping the Linux Standard Base by felixgallo on Friday October 09, 2015 @10:18AM (#10360151)
I boot my rackmount servers in a cage at the dc using a what now?
Re:Debian Dropping the Linux Standard Base by madez on Friday October 09, 2015 @12:08PM (#10360995)
Your use case is a tiny minority which doesn’t provide enough justification to increase the complexity of the default, for complexity being _very_ expensive.
Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:28PM (#10361188)
And this is why Linux user space is going down the tube.

Basically that exact capability is why people adopted Linux in the first place to run the servers that run the net.

I don't see how having a / that can get up and running even when the larger system housed in /usr and such is down for the count, is anything more complex that the piles of VMs and containers that is being advocated today.

Re:Debian Dropping the Linux Standard Base by madez on Friday October 09, 2015 @12:52PM (#10361448)
You are free to set up your system as you wish. I also don’t advocate for removing options. I’m asking for a simple default. Simplicity is very important. If you can’t explain what you are doing to your parents, it is not yet simple enough.

Don’t misunderstand simplicity for triviality for they are not the same. We need to make non-trivial problems simple.

Re:Debian Dropping the Linux Standard Base by spacemanmatt on Friday October 09, 2015 @09:52PM (#10364160)
I run a multiuser shell system for hosting tmux/ssh/irc type usage. It's limiting but it's a labor of love for friends. For anything that matters I use a modern (piles of VMs and containers!) design.
Re:Debian Dropping the Linux Standard Base by felixgallo on Friday October 09, 2015 @01:34PM (#10361827)
Global desktop PC shipments in 2015: ~136mm (http://www.statista.com/topics/1070/pcs/)

Linux desktop penetration: ~1.33% (http://www.netmarketshare.com/operating-system-market-share....)

1.3% * 136mm = 1.77mm

Let's ignore Amazon, Google, Microsoft, Facebook, and so on, each of whom are by themselves rumored or reported to have over a million computers in their DCs. Let's further ignore the long tail of the second tier of providers, who are thousands in number and have merely hundreds of thousands of computers each in their DCs. Let's go on to ignore all of the self serve corporations in the hundreds of thousands of data centers across the world, running Linux or a derivative on thousands to hundreds of computers each.

Let's also ignore all the routers, switches, file servers, and miscellaneous other networking equipment running Linux or a derivative.

Let's further ignore all of the televisions, media players, microwaves, appliances, and other consumer goods running Linux or a derivative.

Let's look only at Android phones, which run an embedded derivative of Linux. The phone market shipped 341.5 million year over year in 2015 Q2 (http://www.idc.com/prodserv/smartphone-os-market-share.jsp). Android had an 82.8% marketshare, so that's 282.77mm.

The number of linux computers that have the ability to boot "a live cd" is 6 thousandths (.6%) of one segment of one part of the linux embedded and server market.

Linux on the desktop has not only been dead for the last 18 years, it's barely a rounding error on a single segment of a single part of the embedded and server market.

By the way, "the complexity of the default" has been fine for over 30 years, and it's still fine. Just because you don't understand it, doesn't mean it's not the right answer.

Re:Debian Dropping the Linux Standard Base by powera on Friday October 09, 2015 @04:57PM (#10363224)
https://news.ycombinator.com/item?id=3519952 discusses the article I remember reading. The comments there (which I haven't read) seem to also disagree with the article.
Re:Debian Dropping the Linux Standard Base by thaumaturgy on Friday October 09, 2015 @06:38PM (#10363659)
Thanks for the link! That article and the comments support your argument better than mine and I have to defer to ChuckMcM's expertise -- it predates mine by a lot, my first experience with Unix-like operating systems was in 1996 and his memory is better than mine anyway.

I'm 100% certain I remember the instructions for partitioning being related to file system corruption, but that may well have come long after the original design of the FSH.

Re:Debian Dropping the Linux Standard Base by 885895 on Friday October 09, 2015 @09:54AM (#10360002)
I nuked /usr on one of my servers for cleaning purposes some 5-6 years ago when I was still quite fresh to Unix. After reboot, I was unable to log in even as root. That was the day I learned not to change the shell of root to anything outside of /bin (I had set it to /usr/bin/bash).

I was able to recover the machine with a LiveCD but still, it was annoying.

Re:Debian Dropping the Linux Standard Base by hiphopyo on Thursday October 08, 2015 @08:13PM (#10357284)
Re:Debian Dropping the Linux Standard Base by codemac on Thursday October 08, 2015 @09:14PM (#10357524)
You should look at Nix and Guix if you like distros with novel file systems.
Re:Debian Dropping the Linux Standard Base by bitL on Thursday October 08, 2015 @10:21PM (#10357766)
Exactly! I wish Gobo and its filesystem structure was used more outside Brazil!
Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:29PM (#10361205)
There is a smattering of users across the globe...
Re:Debian Dropping the Linux Standard Base by avn2109 on Thursday October 08, 2015 @09:26PM (#10357565)
I remember being baffled by the file tree as a Linux n00b, and a scheme like this would be way more discoverable.
Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @11:53AM (#10360876)
One thing about Gobo is that it does not try to enforce any specific layout outside the distro itself. Heck, the last version basically have a legacy layout inside /System/Index.

This so that it is less likely that anything with hardcoded paths will throw a hissy fit.

Frankly Gobo demonstrate the massive flexibility of classic unix tools, as most of it is shell script and symlinks. There is perhaps a few binaries, purely for performance (and those are third iteration, the first being shell script, the second Python).

Re:Debian Dropping the Linux Standard Base by lifeisstillgood on Friday October 09, 2015 @02:36AM (#10358498)
I like the idea here (every app / installable) sits entirely under one directory, all config, binaries etc.

However isn't the problem that we need everyone to agree to do this? Additionally it is nice to have all config in /etc

Re:Debian Dropping the Linux Standard Base by digi_owl on Friday October 09, 2015 @12:32PM (#10361236)
Well Gobo basically don't care, it maintains a replica FHS so that minimal effort is needed to get existing software running.

Heck, it originated as one guy's solution for managing self-compiled programs within his home dir on the university mainframe (or some such).

You can still find Rootless (the bootstrap tool for using Gobolinux in the home directory) on the Gobolinux site, but i can't comment on how well maintained it is these days.

Re:Debian Dropping the Linux Standard Base by Zardoz84 on Friday October 09, 2015 @07:34AM (#10359359)
I should give a try to it. Looks interesting.