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

 



Forgot your password?
typodupeerror
×

Comment From the article.... (Score 1) 81

From the article "Rather than draw from a licensed collection of images, Defendant gathers these images by crawling as much of the Internet as it can, copying and indexing every image it finds, without regard to the copyright status of the images and without permission from copyright owners like Plaintiff,"

I wonder why Google wasn't charged, too? Isn't that how their image search works?

Comment Re:Er? (automatic locale?) (Score 1) 314

A sort of IDE for all the text based config files the way an IDE is a helper for the text code files of a programming language. (But NOT a binary that bypasses the text configs! Which is what systemd seems to be doing, if I've been reading this right.)

But you use a binary, even now to view the text files. Whether you us cat or less or vi or some other editor/viewer, human beings cannot read text files from a log without having to use a binary. That is because what we call text files are merely representational of a text file. Like a binary, though, they are just zeros and ones until some program interprets them for us.

Comment Re:Oh well ... (Score 2) 314

Are you stupid? Modules compiled together are not a "modular" system in the UNIX philosophy at all. They are one program.

Except the separate systemd modules are all seperately functioning executables. That's why if you want to run gnome-shell, you can simply include the logind daemon from systemd along with whatever init system you want to use. Even if you choose to compile all of systemd, it only uses the daemons you turn on. How is that not modular?

Comment Re:Oh well ... (Score 1) 314

> the reality is systemd is a bunch of individual modules

I disagree. Technically you are correct, but the same modularity argument can be made for practically any piece of code bigger than "Hello World". However in practice systemd is shipped as a monolith. I just checked, and even on Genoo with its uber-flexible USE flags and compilation from source, you can't shut off individual features like logging, dhcp, ntp, etc. Most people just install the binaries.

No, systemd is not the end of the world. But it would be the end of running my machines the way I wish to - at least without spending more time and effort keeping it fenced in as you suggest.

Systemd has a configure system similar to the kernel. Like the kernel, where some distros use a "full" kernel and others use a stripped down version, it is up to the distro to decide what fits its need. The same is true with systemd. Take distros running late versions of gnome-shell, which requires the logind module of systemd, all they are including is logind, not all of systemd. Even Ubuntu is using logind with upstart and also sys init scripts.

Nobody is forcing a distro to adopt systemd. If the distro developers do and it impacts you, the complaint should be with the distro developers, not systemd. Maybe the developers have good reason for making the change. Most of them are community based, so it is doubtful that they are doing it just because Redhat is doing it (although Centos and Scientific would most likely change to maintain compatibility).

Even if your distro of choice does change, it shouldn't force you to stop running your machines the way you want too. You can freely mix systemd, upstart and init scripts, using whatever pieces you want for whatever need you have. That applies whether your system is a desktop, server, embedded or whatever.

Comment Re:Er? (Score 0, Troll) 314

It seems most of your problems are just repeated myths about systemd. For instance http://0pointer.de/blog/projec... debunks all of them and there are numerous other sites that do likewise. While I am not a big fan of systemd, I do understand what they are trying to do and it isn't the end of the world like people want to make it out to be.

Comment Re:How about then backporting from BSD to Linux? (Score 1) 314

If BSD's emulation of those Linux systemd APIs is done in a reasonably portable manner, we could then backport the code over to Linux and gain the benefits without being dependent for those functions on the engineering disaster that Lennart has put into process slot 1.

The BSD folks aren't succumbing to systemd's problematic "kitchen sink in slot 1" approach, so their work could be valuable for those Linux distros that are fighting to keep systemd out of their hair.

The BSD "emulation" is a translation layer from linux kernel calls built into various parts of systemd to BSD kernel calls. If you are already running on a linux kernel, what would be the point of a translation layer. It would be like running Wine under Windows.

It seems that the BSD developers are looking at just using the pieces that they think their incarnation of BSD needs. There is nothing to stop a linux distro from doing the same thing. Many already do by adding logind for Gnome while still using upstart or the old init system.

Comment Re:Er? (Score 1) 314

The three services are actually needed.

For what? If you say "to bring more windowsisms to linux" then I can believe it. Otherwise, not so much.

The usefulness of logind can be argued, but centralized management of date/time and locale changes were long overdue. Linux is pretty much the only OS remaining, where application, if needed, can't really know if/when date/time or locale has changed.

Unix (not so much linux) has for a really long time been a multi-user system, where multiple users can use different locales and different time zones. The system itself always ran on UTC. UTC is not supposed to change. Users changing their locale need to log out and back in again. That works well enough for the expected frequency of such changes occurring and doesn't need lots of code to notify every running process AND lots of code in every running process to deal with the change.

As an engineering tradeoff, the Unix way makes sense to me. The poetterix way, not so much. So I don't really buy your "long overdue", no.

Maybe those three services are included because they were replicating the functionality that both upstart and other init methods already provided. Dealing with time zones, system clocks and login/shutdown wasn't something that only became available with systemd. If these three daemons are problematic, then it goes back much further than systemd.

Comment Re:Er? (Score 1) 314

The systemd-localed is simple: it provides the user with capability to change the locale on the fly (and applications with the ability to react on the locale change).

Locale settings are fine without system-level settings. What is wrong with application-specific LC_xxx settings? And why should I be interested in changing locale in the middle of a desktop session?

The systemd-timedated does almost the same for the date and time.

What?! Who the hell changes time on computers? This is not a $5 digital watch! Every reasonable system has got ntpd installed and is set to UTC. The rest is done by selecting the time zone you are in. And stay away from changing time zones by adjusting time! We are not in Windows world where time handling has been fucked up entirely.

And the systemd-logind is basically a dbus wrapper to provide access to log-out/shutdown/etc functions.

Why do I need a daemon to log out from a session?

Think outside the box. Maybe your linux system is embeded in the flight systems of an airliner or vehicle that really does need the capability of changing timezones. Maybe your linux system needs to communicate with other devices that don't deal with system clocks the same way or don't use UTC. And, as for logging out or shutdown, maybe you don't need it, but surely, it is foreseeable that some applications might benefit from it instead of having to each role their own solution.

Look at it this way, some use cases don't need cron, either, but it doesn't mean it isn't useful for those use cases that really do need it.

Comment Re:Er? (Score 1) 314

I would have expected that BSD would be deliriously happy that the evil gaze of Poettering hadn't alighted upon their operating system. Why would you voluntarily infest your system with his daemon spawn?

Because bloody systemd will be needed if you want to run some brain-dead Linux-only piece of crap software. That's why.

Emulating systemd allows that software to work on OpenBSD. On the other hand, emulating it means that (a) its working may remain somewhat on the sane side and (b) that emulation will only be installed if the port requires it, therefore limiting the damage.

And, FYI, OpenBSD could not care less about Poettering and his evil gaze.

Chances are that is false. What is much more likely is that one of the systemd modules, say logind might be required, but not all of systemd. Isn't that how software development is supposed to be -- use an existing library that provides the required functionality instead of everybody building their own version?

Comment Re:Oh well ... (Score 1) 314

Except no one wants MS Windows methods of doing stuff. They've been trying to invent UNIX since the DOS days. Their latest OS is utter hell, so why do a tiny amount of Windows centric NIH kids get to fuck up almost every distro?

This is the biggest fuck up in Linux history, and it will force a mass migration to a BSD.

That's fine, because systemd is not the "windows" way and anybody claiming it is is just blowing smoke. While I prefer upstart to systemd, the reality is systemd is a bunch of individual modules (you know the linux way of one program for one task) that work together. However, when compiling it, you just set switches for the pieces you want to use. You don't have to use all of the modules and those that you do use will coexist with upstart and other init scripts.

There is a lot of fud about systemd, and like I said, it isn't my preference, but it isn't the end of the world that many people want you to believe.

Comment Re:Why Not? (Score 2) 314

Mebbe this will motivate some distro to do a similar; I, for one, would go for a distro without systemd nor Gnome, which I never use. Gnome is expendible. For those who like Gnome, why not do it this way?

There is no need on linux to a translation to system calls. Being built on the linux kernel it just makes the system calls it needs. As for Gnome requiring systemd, it doesn't. It uses logind which is just one part of it. People keep implying that systemd is this huge monolithic init system. It isn't. It is made up of numerous individual daemons that you are free to include or not. For instance, you can use all of your current init scripts or upstart and just include logind if you want to use gnome-shell.

Just like distro's compile the kernel with what features they want to include or not, the same is true with systemd.

Comment Re:Oh well ... (Score 1) 314

Exactly, it would seem this will simply emulate the behaviour for applications that expect it, sitting on a DBUS interface. Since it now seems the whole systemd mess will not go away, I would assume this is the "correct" approach to manage it.

I can only wish non-RH GNU/Linux distrost adopted the same approach.

There is no need to emulate. Any distro can implement what portions of systemd to include or to exclude by simply clicking on the portions they want and off the portions they don't want. Systemd isn't an all or nothing choice. The distros can use as much or as little of it as they please.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...