Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:All linked in /usr ? (Score 1) 58

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 Re:Why? (Score 2) 127

Yes and no.

The basic problem with deb, and rpm, and similar package manager, are that they get hung up on the package name and version.

Meaning that you can only have one version of a particular name installed at any one time.

Want to install another version? Either you remove the old version or you change the name to avoid a conflict. But changing the name plays havoc with the dependencies tracking.

If deb and/or rpm was changed so that the manager could handle tracking multiple versions of the same package name, the need for the likes of snappy, xdg-app, or a myriad of similar systems would not be needed.

You can see this if you check out NixOS/Guix or Gobolinux that have implemented slightly different solutions to the same problem.

Comment Re:kinda dissapointed... (Score 1) 187

Yeah, choice. Like how Wayland depends on logind depends on systemd-as-init.

Damn it, one screwball in the dependencies chain and Gimp depended on systemd-as-init.

Hit update at that time and boom your perfectly functional distro install gets a init-ectomy.

To a init that will refuse to boot if you have a vestigial entry sitting around in fstab, no less.

Comment Re:kinda dissapointed... (Score 1) 187


Update to a recent Gnome and it will bellyache about logind, that in turn is part of system. End result, what used to be a desktop that can run on top of any init requires a specific init.

Moving forward i am expecting to see similar with their cron replacement, their networking and firewall stuff, etc etc etc.

This where before things would not care if you booted via sysv, openrc, upstart, bsd rc, or a flat shell script with a bunch of commands.

Comment kinda dissapointed... (Score 1, Interesting) 187

That Torvalds has bought the whole "just a init" marketing spiel surrounding systemd.

It is a init.
And a cron.
And a inetd.
And a network manager.
And a dhcp client.
And a (caching) DNS client.
And a session/seat manager.
And a firewall manager.
And a boot manager.
And a /dev manager.
And soon to be a tty manager.

Its proponents may claim that all those are optional.

From a init point of view sure.

But from a desktop point of view, wanting to use any of those make systemd-as-init mandatory.

Comment Re:linux hard to install and use for desktop users (Score 1) 187

Gnome, KDE, heck even XFCE or LXDE/LXQT would do.

What it comes down to is not the interface, but that it comes preinstalled and configured for the hardware it runs on.

OSX comes preinstalled on Mac (basically a massive dongle these days). Windows comes preinstalled on a range of x86 based devices.

The buyer unpacks, turns on, enters some basic account data, and starts using.

Comment Re:linux hard to install and use for desktop users (Score 1) 187

What people gloss over is that you don't install OSX on your own. You buy a Mac (the worlds biggest dongle, imo) and it comes preinstalled.

Similarly with Windows, outside of the build it yourself enthusiasts people buy Windows preinstalled on some kind of x86 device.

Look at Chromebooks and you see preinstalled Linux.

Look at Android and you see preinstalled Linux.

Netbooks (that Chromebooks could be considered related to) started out as preinstalled Linux, but MS and Intel joined forces in smothering that baby in the crib.

Comment Re:Can linux survive? (Score 1) 323

Having done a bit of digging, and perhaps some soul searching, it seems that Poettering, and others, think that a tightly coupled system is the only way to build a OS.

This because they see generic distros, like Debian and Gentoo, have in effect dug themselves a hole thanks to the number of permutations involved in packaging (though with Gentoo being compiled by user/admin rather than distro maintainer it may not be fully correct to include them).

But to go from saying distros may have bitten over more than they can chew, to saying that everything between kernel and desktop needs to be a tightly coupled whole is quite the leap.

Yes, distros can be built to be highly specialized, and has been so since the early days. But that is not an excuse for making the software that goes into making a distro tightly coupled.

Also, way to much of what is happening above the kernel is happening from the desktop environment (Gnome in particular) down.

Take dbus for instance, it balks at talking across user accounts. But if it was amended to do so, user accounts become sandboxes.

But instead we get the whole rigmarole of cgroups and namespaces, managed by systemd.

Comment Re:speaking as an engineer, it happens. (Score 1) 323

Torvalds do maintain some ground rules for accepting patches though.

One of them is that they do not break userspace.

This involves making sure that any interfaces exposed to userspace processes behave the same across versions.

When a patch(-set) violates this, the developer(s) behind it will be at the receiving end of some nasty language. In particular if they refuse to acknowledge the breakage, and/or claim it is userspace that should be corrected.

Comment Re:speaking as an engineer, it happens. (Score 2) 323

Yeah i have been wondering about GregKH lately.

He may have produced some excellent code over the years and done a nice job maintaining stable kernel releases. but as of late he seems to have gotten very "one true way"-ish.

Not only the snark regarding maintaining a independent udev, but also the pushing of kdbus into the kernel when the gains are at best questionable.

As best i can tell the forces in the background pushing to get kdbus accepted are the car manufacturers and others wanting to use Linux in commercial embedded hardware.

This because they are coming from other platforms where using a RPC for everything (including the likes of moving massive amounts of raw streaming media data around) was norm, and they latched onto dbus as being the same thing on Linux.

But dbus performance sucks compared to what they used to use, and rather than locate alternatives (like say netlink) they are pushing to get a dbus derivative into the kernel so they can continue their old ways in a new "land".

Frankly i am starting to regret my support for Nokia's Maemo project from years back, as more and more it seems like everything that is, well, crapifying Linux these days seems to have originated from that project.

More and more it feels like very heavy corporate and government interests wants to turn Linux into Windows, with little regard to the potency of *nix concepts.

Slashdot Top Deals

If all the world's economists were laid end to end, we wouldn't reach a conclusion. -- William Baumol