Slackware 10.1 Beta And Pat's Health
phreakuencies writes "The ChangeLog in slackware-current got a distiguished update today on Jan 22: Patrick Volkerding updated us on his health condition stating he is not back in perfect shape but getting more medical tests and results. The initial phrase on the ChangeLog: 'I'm going to call this Slackware 10.1 beta 1, because we're at a state where things are relatively stable.' Read up here"
Patrick could just post a complete changelog of his health?
Slackware got mostly replaced by Gentoo on its position of "zealot distro", but Gentoo+Portage requires helluva horsepower under the hood unless you want to wait a week for OpenOffice upgrade. Slackware still is a viable choice for everyone who wants to learn the inner workings of Linux and uses some CPU running below 1GHZ.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
I think this "event" reflects the way in which most open source projects are lead.
Certainly you won't see in a commercial product news about the health of the developers as items in a ChangeLog.
However, in open source, the freedom to fork is often given as an excuse for allowing one person to be the benevolent dictator of the whole thing. On good merits, it seems, because many argue that if it weren't for that, things would never get done and stuff. But this "dictator" stuff gives the project owner a lot of power and a lot of discretion, and someone said once "power corrupts".
Is it ok to notify the community about how the leader feels and where he's headed from a medical perspective? Yes. But, is the official changelog of the distribution the right place to do it? Would such a thing be done in a commercial product?
you can get precompiled packages for gentoo, no need or point most of the time compiling things yourself.
but slack still has it's following, and is fundamentlly different from gentoo - and damn, it's one of the old and still going distros.
world was created 5 seconds before this post as it is.
"Patrick Volkerding".
:-)
However, it seems that there has been a bug fix for this package's recent problem
but I wonder: assuming he has to pay for medical care (I'm British, sorry) - I hope he makes enough money from this project to adequately cover these costs.
Here is my real beef - I love open source, but it pisses me off when I speak to people in business when they talk about free software in terms of monetary cost. I believe that if you regularly use and rely on certain software - OS or not - that you should be obliged to pay something in return to the support the process.
Frankly, there are a number of businesses who really rely on this software and refuse to believe that they owe anything in return - money or code.
Sorry folks, rant over...
learn the inner workings of Linux and uses some CPU running below 1GHZ
You mean iPod?
This struck me... I use Slack on two *really slow* PCs (233 Mhz) and it makes them perform just fine. And yet I've never paid Pat a dime. I think it's time I started a subscription. What about you?
I'd go further than that, since Slackware is his one-man-show baby, people who use it are very much interested in both his health and what will happen if the worst comes to the worst.
A couple of years ago (or maybe even now for outsiders), people were wondering what would happen if Linus went one-to-one with a bus. That was actually a reason not to adopt Linux. Now we all know that people like Andrew Morton and Alan Cox are available and experienced.
What way would people go if Slackware went down the tubes? Debian? I know I found Red Hat incredibly frustrating when my ignorance and Unix inexperience meant I had to leave Slackware and move to something easier to configure. In the end it was SuSE 5.0 I turned to, it's PCnfs printing capabilities worked 'out of a box'. Not sure I'd see SuSE as a migration path for Slackware users nowadays though.
Get well soon.
Mielipiteet omiani - Opinions personal, facts suspect.
This guy got finally reasonnable. Instead of trying to take care of by himself, he finally went to a doctor, and, best part : Stayed with the same doctor
Of cours, any doctor usually start thinking of the most plausible and statistically significant cause of disease. Usually patient should come back and only if no improvement has been seen, then only the doctors start considering more unlikely or rarer diseases.
But if the patient is unhappy with the first diagnosis of the first doctor and moves to another doctor, the new will start over again from the very beginning.
It's OK to try change doctors when you're not very sick and when you try to find a nice doctor who you like to have him as the one who you usually refer first to.
BUT when someone health is compromised HE SHOULDN'T keep switching doctors. He should try to stay with one (and eventually have him refer to other colleauges if he need more help).
Because each time a patient siwtch doctors, he loose time because of this start-over-again.
And I'm not speaking about the economical problems : doctor switching reases the health cost a lot because a lot of things (lab exams, etc...) are done twice or thrice.
It's a big problem we have here in Switzerland.
There's some work to avoid this kind of redundancy : One exemple of such project in Geneva (CH) is e-toile (Sorry website in french, you have some english info here).
We hope that by building secured networks, doctors could share some information and avoid repeating the same stuffs all over again.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
One of Pat's logs mentions that he was diagnosed with and being treated for infective endocarditis. The medical literature I've read informally refers to that disease as IE.
I think we all know what IE can do to your system. I would have thought Pat would have known better than to mess with it. Perhaps he should spend a little more time reading Slashdot? At any rate, the cure is pretty simple.
This is good news for me. I've been waiting rather impatiently for the next release of slackware. I've tried every distro that offers a download and slackware is the only one I liked. I liked it enough to get a subscription. I'm sure Pat would appreciate it if some of you did the same.
GETPKG - Package Management for Slackware
But since Slackware doesn't offer OpenOffice packages, you have no choice but to compile. I use both (3 slackware boxes, 1 gentoo). They each have their merits to us zealots.
In my prior work we were doing customisation work on our companys own product. Most customisation was done my team of 1 Programmer, (1/3)Project Manager and (1/2)Grapician. Sometimes Pm and graphician being the same person. Programmer was generally doing one project at time. Project manager was managing 2 or 3 and graphician was doing mostly one at time, but was resereved only for hald of the time for a project. Typical project lasted 2 months. Getting specification and connectons from client has half the work.
Employees got sick once in a while like people do.
There was allways the trouble to explain customers.
The usual question was. Why have you not replaced him(her). Our project is prime importance.
a) 25 some will most likely be sick 2 days, geting new programmer to understand takes longer.
b) Puting people in middle of half written code that does not do what is needed, usually means large chunks being rewritten, when original author knows what is missing and only adds that.
c) a lot of specification was usually on the air, and doing the code to interface was the minor part.
d) We sure did not have spare developers.
e) Yes, they all are.
Beside the fact that you CAN install a program like OOo without a package or without compiling,like, by using a installer!
"The day Microsoft makes a product that doesn't suck is the day they make a vacuum cleaner."
I think Debian and Gentoo are the obvious alternatives. Slackware people tend to compile a lot of their own stuff anyway since the default distribution is a bit light on the packages (no OOo for example), and there's a very nice port of emerge to slackware. Debian is quite slack-like but may be too political for many slackers.
I am trolling
Portage doesn't need that much horsepower, just leave it on overnight. I can't do that, but 4 hours a day is quite enough to keep my 800mhz Duron up to date (and it has pretty much everything major installed). nice -n 19 emerge -u world, then your system is just as responsive and it's upgrading. Slackware is still a nice distro, but its lack of a dependency manager hurts it.
I am trolling
I've been using Slackware since it diverged from SLS so many years ago and I'd have to say that you are 100% correct about Debian... nice idea but if I wanted politics, I'd tune in to CSPAN. Their rabid use of GNU/everything has utterly and totally turned me off of the distribution. Gentoo? I don't think so. I think that I'd move to something like Vector Linux which is Slackware based and has a more sensible set of installer defaults (I use my own tagsets though already). The only real reason I'm not using Vector currently is because the ASCII art penguin has to go for starters but more importantly, Slackware is still the 'root' of it and why go with a little offshoot that doesn't change much at the current time?
I'm going to call this Slackware 10.1 beta 1, because we're at a state where things are relatively stable.
:-)
WTF!
He shouldn't let his health condition affect what he labels the Slackware versions!
Beware: In C++, your friends can see your privates!
I have thought of that for one machine of mine (the firewall/proxy), but there is always that one problem: Linux simply supports far more hardware than any BSD variant. Linux hardware support used to be a major issue, now it is almost a given.
/. suggested a couple of years back that Linux would one day be mainstream and 'Uncool', and that people would migrate to BSD. I thought they were joking . . .
Funny, someone here on
Mielipiteet omiani - Opinions personal, facts suspect.
What is there to wonder about? Clearly the bus would be completely and utterly destroyed.
Maybe. IF they allow you to continue to see doctors after the first says there is nothing they can do. IF there is enough money to pay for the tests you need. (Of course if it is life or death it is done, but we do the work here in that case too, when the condition isn't that serious though there may be lines)
Its all a maybe. There are many people in Canada who come to the US for treatment because it is better. You pay for it, but you get better treatment. The reverse is also true because for some things it is better to live under a system like Canada.