Nobody had to reboot when they plugged in a USB device -- we had triggered scripts with udev long before systemd came along.
I'd like to point out that I'm quite familiar with issues like adding "service ipsec restart" to/etc/ppp/ip-up.local so that services start when others do; but its not that hard, and certainly didn't require the flaming pile that is systemd.
I've never understood people with this mentality. Why do you believe something inevitable just because it is ubiquitous?
The OSS sound system disappeared in favour of ALSA, XFree86 vs Xorg, the LVM changes come to mind, etc.
Many many things in open source are up for simply flipping because there's a better option. As soon as a better option to systemd is available, I sure hope it gets jumped on because I'm quite sick of systemd already myself.
That's a fallacy -- you have to assume the same thing with closed-source software -- there's no guarantee that the flaw wasn't discovered as soon as it was introduced then either. The problem is that you have no easy way of testing which versions of the software have variations of that flaw without the source code.
My mother-in-law always orders her steak medium but wants there to be no pink visible inside. We always correct her order to well-done immediately after she orders because she returns any steak with pink visible because like many people with red meat, she doesn't understand the difference between 'not cooked' and 'still pink'.
Having bugs is an inevitability what with how software is written by fallible humans.
How those bugs are identified, handled and fixed is the issue. In proprietary software, the OpenSSL bug might not have even come to light as it did, and a fix certainly wouldn't have been released as immediately as it was.
You misunderstand the value of F/OSS. It is not that our software is bug-free and theirs is buggy, its that we can see and fix our own bugs and not sit on our thumbs waiting for a fix.... cf http://nakedsecurity.sophos.co...
If that's what you're telling yourself, maybe you should wonder about your own defense mechanisms rather than wishing people wouldn't call you names.
I don't like being called an idiot either, but a wise person once pointed out that the things we like least being said to us are most likely to contain nuggets of truth.
Would you say any less to someone who willingly worked for a tyrant, or allowed their government to be tyranical? Being a sucker is being a sucker and while most people seem to prefer not having their nose rubbed in it, that simply makes them part of the problem.
It is only on incredibly rare occasion that I've had to tweak a configuration file on Linux doing an update.
I am a little perturbed however with the new Fedora default of "reboot to update"... (you can install a separate updater that doesn't require reboots).
You seem to have missed his point entirely; Windows 7 is unaffected by this current silliness, which cuts productivity by forcing people to comply with update requirements.
I have a lot of customers who upgrade their PCs a few at a time... as they upgrade, they get new versions of Office, and then inevitably call and complain about how the documents are changing or can't be opened by other users. Its not uncommon, and its really annoying.
Unskippable menus and other issues are coming up but honestly, the only thing stopping me from loading up on more BD movies is that ~ $30 price tag for new releases. There's just no way I'm paying more than $15-20 for a movie, period, so I just don't bother anymore.
Its not a technicality at all. You're thinking marketing not reality.
That's like saying clothing being made of cotton is a technicality and cotton isn't important.
The fact that Linux exists allows for a lot of other things to exist that you wouldn't have otherwise, even though the average person is unaware of it.
Most of the ISPs I've dealt with here in Canada do not offer routable IPv6 allocations to users. They certainly don't readily offer static ones for business use like they do with IPv4.
Slashdot Mirror
For all I know, he's a great developer who expects people to solve real-world problems in a way that makes users' lives better.
Nobody had to reboot when they plugged in a USB device -- we had triggered scripts with udev long before systemd came along.
I'd like to point out that I'm quite familiar with issues like adding "service ipsec restart" to /etc/ppp/ip-up.local so that services start when others do; but its not that hard, and certainly didn't require the flaming pile that is systemd.
I've never understood people with this mentality. Why do you believe something inevitable just because it is ubiquitous?
The OSS sound system disappeared in favour of ALSA, XFree86 vs Xorg, the LVM changes come to mind, etc.
Many many things in open source are up for simply flipping because there's a better option. As soon as a better option to systemd is available, I sure hope it gets jumped on because I'm quite sick of systemd already myself.
That's a fallacy -- you have to assume the same thing with closed-source software -- there's no guarantee that the flaw wasn't discovered as soon as it was introduced then either. The problem is that you have no easy way of testing which versions of the software have variations of that flaw without the source code.
You have no idea how consulting works, do you?
I can tell them what the right thing to do is until I'm blue in the face, its still their money and their decision to make, and mine to work with.
The stat you're quoting is "how many of the things we're designed to look for do we find" not "how many of the things that cause problems do we find."
Anti-virus software doesn't work because MOST problems now aren't and don't look like viruses.
My mother-in-law always orders her steak medium but wants there to be no pink visible inside. We always correct her order to well-done immediately after she orders because she returns any steak with pink visible because like many people with red meat, she doesn't understand the difference between 'not cooked' and 'still pink'.
Having bugs is an inevitability what with how software is written by fallible humans.
How those bugs are identified, handled and fixed is the issue. In proprietary software, the OpenSSL bug might not have even come to light as it did, and a fix certainly wouldn't have been released as immediately as it was.
You misunderstand the value of F/OSS. It is not that our software is bug-free and theirs is buggy, its that we can see and fix our own bugs and not sit on our thumbs waiting for a fix. ... cf http://nakedsecurity.sophos.co...
If that's what you're telling yourself, maybe you should wonder about your own defense mechanisms rather than wishing people wouldn't call you names.
I don't like being called an idiot either, but a wise person once pointed out that the things we like least being said to us are most likely to contain nuggets of truth.
You don't seem to understand the words he uses, this would be precisely why he defines things so strictly for you.
Political correctness means something completely different from what he espouses there.
Would you say any less to someone who willingly worked for a tyrant, or allowed their government to be tyranical? Being a sucker is being a sucker and while most people seem to prefer not having their nose rubbed in it, that simply makes them part of the problem.
He defined questions to have specific meanings when their original meanings were not necessarily specific enough for someone as pedantic as he is.
He has good reasons to do so if you understand such things.
It is only on incredibly rare occasion that I've had to tweak a configuration file on Linux doing an update.
I am a little perturbed however with the new Fedora default of "reboot to update" ... (you can install a separate updater that doesn't require reboots).
You seem to have missed his point entirely; Windows 7 is unaffected by this current silliness, which cuts productivity by forcing people to comply with update requirements.
They're supporting an OS people use, and not one that people don't even like.
http://www.zdnet.com/just-how-...
Every grad coming out of our local college's IT program is versed in Linux and a number of other actually common technologies.
Have you talked to your local college about which programs offer Linux training so you can watch for those on resumes?
I have a lot of customers who upgrade their PCs a few at a time ... as they upgrade, they get new versions of Office, and then inevitably call and complain about how the documents are changing or can't be opened by other users. Its not uncommon, and its really annoying.
If the current state of FOSS is what you call failure, what do we call things that aren't ubiquitous and successful?
So you didn't bother downloading the offline http://www.libreoffice.org/get... documentation?
I don't feel that bad for you ... obviously you're the type of person Microsoft is targeting.
Unskippable menus and other issues are coming up but honestly, the only thing stopping me from loading up on more BD movies is that ~ $30 price tag for new releases. There's just no way I'm paying more than $15-20 for a movie, period, so I just don't bother anymore.
Its not a technicality at all. You're thinking marketing not reality.
That's like saying clothing being made of cotton is a technicality and cotton isn't important.
The fact that Linux exists allows for a lot of other things to exist that you wouldn't have otherwise, even though the average person is unaware of it.
I'm reminded of a previous Slashdot story ... http://hardware.slashdot.org/s...
For all we know, 11000 of those were never unpackaged.
The version of Android sold on those phones is only locked by the phone manufacturer, not Google.
This is more like the car companies suing because they had to make cars that run on gasoline because gas stations primarily sell gasoline.
Most of the ISPs I've dealt with here in Canada do not offer routable IPv6 allocations to users. They certainly don't readily offer static ones for business use like they do with IPv4.