Debian has some poison people in it, having lost the decision over systemd they should have gotten on board
Pardon my French, but that is a bullshit philosophy. It's like: "The fascists won the election. Let's all get on board and work with them. If they won't, they are sore losers."
For one thing, they are using systemd to query and make changes to the system config, since they have GUIs that need to do this. IMO they should be written to fall back to the old way of doing this directly if systemd is not present, but the tradeoff is extra programming and maintenance work.
The problem with the Linux community isn't that they fight. It's that:
1) They don't know how to compromise 2) They don't know how to ever STOP fighting.
It ain't just the linux community. Look at islam vs every other religion. Look at national politics. Look at yes-manmade-climate-change vs no-manmade-climate-change. Look at yes-carbon-sequestration vs no-carbon-sequestration. Look at yes-nuclear vs no-nuclear. Look at just about every area of contention in present-day society.
commenting anonymous not to undo mod points. I just upgraded some testing machines with a init system other than systemd, and yes, they were infected with systemd without any warning and any approval of my part.
More details. How did the "infection" occur? Magic? Did your installation include Gnome? If so, why?
A static IP for your shared host is usually cheaper than SSL. However, they're not going to let you use your free SSL and will charge you for their own SSL anyway, because they have the control.
Who is "they". The VPS I rent is shared (by me) to various parties - shared hosting. It's my VPS. I control its certificate. There is no "they".
bye, then. you didn't care enough to get involved enough in debian to have any say in the matter. so good riddance.
Lose the hostility, coward. What do you care whether moves on? As a FreeBSD user, I can assure you he won't be sorry learning and using it, so nobody is a loser.
Overprovisioning and TRIM are orthogonal solutions to the problems of decreasing performance and limited device life. Only a fool leaves his seatbelt unattached because he has an airbag.
Broken hardware is no excuse for refusing to implement a standard ATA command. Broken hardware is dealt with by caveat emptor and warranty. You don't try to design your product so that it can work around any kind of broken hardware which has been randomly swapped into it.
Your question has already been answered, so you can stop wondering. No speculation is necessary.
Hint: Trim Enabler is not a driver which has been "developed", it is something that applies a binary patch to the existing driver to remove the gratuitous checking for the string "APPLE SSD".
So are you really asking what could be wrong with Apple categorically refusing to implement a standard ATA command that is essential to good SSD performance?
Or maybe, I don't know, we should be comparing routes and population of cities at the route terminii.
For example, Tokyo (pop. 13.4 million) to Osaka (pop. 2.7 million) is 500 km. New York City (pop. 8.4 million) to DC (pop. 0.6 million) is 364 km. The DC-Baltimore Metroplex is 9.3 million.
If you look at it that way, the disparity is much less. Nobody is suggesting high speed trains to connect every town in the US to every other town, but their complete absence from any routes at all is just third world primitive.
777 cruise speed is 900 km/h, but the actual average speed from embarking to debarking - "block speed" - which includes loading, waiting for takeoff clearance, taxiing, takeoff, climbout, a percentage of adverse winds during cruise, waiting for landing clearance, landing, taxiing, and unloading - is a good deal lower.
A block speed of 700 km/h, particularly over routes that are not very long, and match train route lengths, would not be too far off the mark. That's a lot closer to a train with a block speed not far short of 500 km/h, than is a naive comparison of 500 km/h to 1000 km/h.
A train's block speed is also less than its "cruising" speed, but many of the factors that work against airliners are either absent or of reduced magnitude.
Nothing wrong with conservative in this context. Also, most people don't understand, but FreeBSD ports/packages are essentially individual rolling releases, and are not tied to the OS version. E.g., the current version of bash for the release 8 branch (yes, it's still supported) is 4.3.30. Release 9 - 4.3.30. Release 10 - 4.3.30. If you upgrade 10.0 to 10.1, the packages remain exactly the same version, and are stored in exactly the same repo directory. If you jump a major version, they actually switch to different repo directories, so presumably there are SOME differences.
Keep in mind, though, that FreeBSD 9.2 hits EOL the last day of this year. I imagine FreeNAS is the same; it's just a derivative.
I'm a little more cutting edge, or ambitious, as the case may be. My 24 TB of files are sitting on a computer I call a "file server", not a "NAS" (there is no meaningful difference AFAIK). It is running FreeBSD 10.0, and I will upgrade to 10.1 soon.
You can help me out by telling me why you use FreeNAS instead of FreeBSD. I am guessing, from what I've read, that the only appreciable difference is that the former has some added graphical file-server control utilities.
Slashdot Mirror
Coca-Cola only has one line of business, and that is soft drinks. Eventually all one trick ponies meet the same fate.
Yeah. Right. Um.
FTFY. And the answer is, yes, it is nuts. What's it like completely missing the point?
Pardon my French, but that is a bullshit philosophy. It's like:
"The fascists won the election. Let's all get on board and work with them. If they won't, they are sore losers."
For one thing, they are using systemd to query and make changes to the system config, since they have GUIs that need to do this. IMO they should be written to fall back to the old way of doing this directly if systemd is not present, but the tradeoff is extra programming and maintenance work.
It ain't just the linux community. Look at islam vs every other religion. Look at national politics. Look at yes-manmade-climate-change vs no-manmade-climate-change. Look at yes-carbon-sequestration vs no-carbon-sequestration. Look at yes-nuclear vs no-nuclear. Look at just about every area of contention in present-day society.
More details. How did the "infection" occur? Magic? Did your installation include Gnome? If so, why?
That's not good enough. Not by half. The hotel manager should be charged criminally, found guilty, and sent to prison for flagrant fraud.
Who is "they". The VPS I rent is shared (by me) to various parties - shared hosting. It's my VPS. I control its certificate. There is no "they".
Railroading by a small elite.
FTFY.
Lose the hostility, coward. What do you care whether moves on? As a FreeBSD user, I can assure you he won't be sorry learning and using it, so nobody is a loser.
Yeah, correct, the debate is over, coward. I've moved on, to an OS developed by adults. FreeBSD. I'm happy; you're presumably happy; so it's all good.
Overprovisioning and TRIM are orthogonal solutions to the problems of decreasing performance and limited device life. Only a fool leaves his seatbelt unattached because he has an airbag.
Broken hardware is no excuse for refusing to implement a standard ATA command. Broken hardware is dealt with by caveat emptor and warranty. You don't try to design your product so that it can work around any kind of broken hardware which has been randomly swapped into it.
Overprovisioning and data compression are in no way a real substitute for TRIM. Anyone who thinks so is not thinking clearly.
Your question has already been answered, so you can stop wondering. No speculation is necessary.
Hint: Trim Enabler is not a driver which has been "developed", it is something that applies a binary patch to the existing driver to remove the gratuitous checking for the string "APPLE SSD".
So are you really asking what could be wrong with Apple categorically refusing to implement a standard ATA command that is essential to good SSD performance?
I see no evidence that anyone who sounds sane does suspect Mossad.
Or maybe, I don't know, we should be comparing routes and population of cities at the route terminii.
For example, Tokyo (pop. 13.4 million) to Osaka (pop. 2.7 million) is 500 km.
New York City (pop. 8.4 million) to DC (pop. 0.6 million) is 364 km. The DC-Baltimore Metroplex is 9.3 million.
If you look at it that way, the disparity is much less. Nobody is suggesting high speed trains to connect every town in the US to every other town, but their complete absence from any routes at all is just third world primitive.
777 cruise speed is 900 km/h, but the actual average speed from embarking to debarking - "block speed" - which includes loading, waiting for takeoff clearance, taxiing, takeoff, climbout, a percentage of adverse winds during cruise, waiting for landing clearance, landing, taxiing, and unloading - is a good deal lower.
A block speed of 700 km/h, particularly over routes that are not very long, and match train route lengths, would not be too far off the mark. That's a lot closer to a train with a block speed not far short of 500 km/h, than is a naive comparison of 500 km/h to 1000 km/h.
A train's block speed is also less than its "cruising" speed, but many of the factors that work against airliners are either absent or of reduced magnitude.
I didn't have any trouble at all downloading the ISO the day BEFORE the release announcement appeared.
That sounds rather circular to me, but I get the idea. FreeNAS is more of a click-and-use solution.
You're trying really hard, but it's not working. Slackware 1.0 boasted Kernel source and image at .99pl11 Alpha. Yggdrasil had 0.98.1 version of the Linux kernel.
1.0 to 1.0 or it's a bullshit comparison.
Your interesting anecdotes do not in any way contradict the FACTS. I was using SysV in the early 80s. So what.
You might as well point out that BSD's first release was in 1977. Doesn't in any way change the 1.0 dates for FreeBSD and Linux.
Nothing wrong with conservative in this context. Also, most people don't understand, but FreeBSD ports/packages are essentially individual rolling releases, and are not tied to the OS version. E.g., the current version of bash for the release 8 branch (yes, it's still supported) is 4.3.30. Release 9 - 4.3.30. Release 10 - 4.3.30. If you upgrade 10.0 to 10.1, the packages remain exactly the same version, and are stored in exactly the same repo directory. If you jump a major version, they actually switch to different repo directories, so presumably there are SOME differences.
Keep in mind, though, that FreeBSD 9.2 hits EOL the last day of this year. I imagine FreeNAS is the same; it's just a derivative.
I'm a little more cutting edge, or ambitious, as the case may be. My 24 TB of files are sitting on a computer I call a "file server", not a "NAS" (there is no meaningful difference AFAIK). It is running FreeBSD 10.0, and I will upgrade to 10.1 soon.
You can help me out by telling me why you use FreeNAS instead of FreeBSD. I am guessing, from what I've read, that the only appreciable difference is that the former has some added graphical file-server control utilities.
Or ... I've got an idea. Stick with X11. It works perfectly fine. Let the losers waste their time developing Wayland for some other OS.
Oh, and before somebody asks, Linux 1.0 was released 14 March 1994.
FreeBSD was there first.