Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Re-buy (Score 1) 368

someone who has never bought anything from the iTunes Store

I wasn't referring to them. I thought we were talking about people who care enough about iTunes to complain about it stopping working. They probably still use iTunes because in the past they have bought something from the iTunes Store.

Comment Legislators are both busy and bought (Score 1) 309

So why aren't we fixing the real issue of overly broad copyrights?

Because that would require national legislatures to actually do non-trivial work. They're already busy enough deciding whether and how much to spend on particular military, entitlement, and military entitlement projects. Nor have they seen any evidence that reforming overly broad copyright would win them more votes, especially when Hollywood promises them essentially free ad time to reach their constituents during election season but only if they "behave" (FOX News; The Hollywood Reporter).

Comment Import duties (Score 1) 309

Such a copyright term applied to works with an individual author would violate the Berne Convention, which all World Trade Organization members must adopt. The Berne Convention requires a minimum term of 50 years after the death of the last surviving author or 50 years after publication for works with a corporate author. A country adopting such a copyright term for works with an individual author would get kicked out of the WTO and see its exports in unrelated industries become subject to prohibitive import duties.

Comment Re:systemd, eh? (Score 1) 494

Systemd "won" because of the choices of distibution maintainers, not the choices of linux users or the linux ecosystem. The rise of systemd occurred in a top-down manner, which is the exact opposite of how traditional open source software gains acceptance and widespread usage. Somehow it's not surprising that systemd itself (the software) operates in a similar top-down manner, forcing adoption by creating new dependency issues.

Was that an exercise in truth inversion?
The Linux ecosystem is exactly what made systemd "win". And the rise of systemd occurred in a bottom-up manner actually.
systemd actually didn't win anything, it just allowed the streamlining of using the Linux kernel specific features that nobody used because of catering to the lowest denominator. I was not surprised at all at how fast true admins got rid of sysvinit or even Upstart.
On the machines I control, I've done this more than 15 years ago, going with simpleinit-msb for most of this time, before having to switch to an alternative because maintaining it was leaving me sometimes with security vulnerabilities to fix alone.

Comment Re:Upstart or Systemd? (Score 2) 494

It worked.. except when it didn't. I should not have to hack my init scripts just because I have iSCSI or Clustered Fileystem mounts. Init was made in a time when the boot dependencies are more flat and don't do well at all when your setup requires network+daemon before the filesystem can be mounted.

Exactly! When you have several layers on top of your block devices, like RAID and LVM, it's even worse.
It was such a pain before, despite the LVM or multipath daemons, I was never sure the servers would reboot correctly, or the config freeze or corrupts itself.
Such a nightmare before systemd tackled the problems and sometimes the bugs in kernel or daemons, now it just works.

Comment Re:Upstart or Systemd? (Score 1) 494

"And your vision of systemd is wrong by the way : educate yourself please."

How about you tell me then. Apparently you're such an uber admin that surely it'll be no problem to list the advantages of systemd compared to init. Right?

I won't do your work for you, and you must be a pretty bad one to talk about things you don't even know about.
If reading skills and understanding skills are so challenging to you, you won't understand a thing, which is probably what happened already, given the copious amount of documentation available on systemd. There never were any for sysvinit and its scripts, and a very bad one for Upstart.
Besides, you need experience with sysvinit or Upstart to understand the biggest advantages of systemd.
Given my experience, I just don't take people that say sysvinit (or Upstart) had no problem seriously, less of my time lost this way.

Comment Re:systemd is a bad joke (Score 0) 494

if I had mod points, I'd mod you as troll.

its not the 'basement dwellers' - those guys have zero experience in unix, given that they are alive less than 20 years, usually, and they know only what they've learned during the obama years and not much before that.

the rest of us who have used and managed unix since the 80's have to dump WHAT WORKED WELL and move to some new shit that clearly has issues, does not fit in or belong very well and is being forced on us.

Stop making fool of these veteran good unix sysadmins please. I will not associate with some fool like you. You people that know nothing love to give yourself a false authority by saying this nonsense everytime. But a good sysadmin will see through you without any problem.
You trolls are so nonsensical that you say Upstart WORKED WELL and was available in the 80. Linux is not Unix BTW, if you were a seasoned Unix sysadmin, you would loathe Linux more than systemd, systemd is only possible because of Linux.
You are wrong on all counts, so blinded by your hatred for something you don't even understand, it's pathetic.
I've encountered very few admins that even understand how a Unix-like boots anyway, lots of seasoned admins just have no ideas.
I've encountered far more Linux sysadmins that had this knowledge than anything else.
At best you're one of them.

see, the value of a craftsman is in his knowledge and experience of his tools. some people spend decades learning how to use their tools and work in their trade and the time shows; experience is worth having and paying for!

what happened now: some newbie decided the old way was not good enough and decided to change it all out, for no good reason at all (I have not yet seen a good reason to reinvent a wheel that has been working for longer than most of you have been ALIVE).

You're wrong, plain and simple!
Upstart was trying to solve lots of problems of sysvinit that a seasoned Unix admin should know about, it even used dbus.
And the decision to use systemd by default in Ubuntu was the distro maintainers choice.
No good reason to make better than sysvinit? I've seen reasons 16 years ago, that's why since then I never installed sysvinit init anymore on my own made Linux OS. And yet, in my work environment, I'm still to this day the most knowledgeable around about how all this sysvinit crap works, be it SYSV or BSD style.

faster startup is not a reason; this isn't a media player and linux still does not startup in 3 seconds or less, so what's the point of 'faster startup' when its really not fast enough to justify this forklift upgrade of sorts?

If that's the only reason you know about, it just confirms you know nothing about systemd. This is not even one of the main advantage of systemd since years.
The dynamic nature of the Linux kernel and its devices is one main reason.

Slashdot Top Deals

This file will self-destruct in five minutes.

Working...