Eh, I can assure you it's not just the 10-14 year olds out of a job when print media dies (and it will, but probably not real soon).
I deliver newspapers (motor route, 50 miles, ~250 papers total run -- a relatively small route) seven days a week and I guarantee I'm well out of the 10-14 age range. Most carriers out this way (rural New Hampshire) are at least 30+ -- a few are _much_ older folks (75+) contracting to supplement social security payouts who probably won't live long enough to be out of a job when it comes right down to it.:)
I can't disagree that the death of print media is a Good Thing, though. Frankly, production-related issues (web is faster, trees are good, etc...) are not nearly as important as two very immediate issues: you have to pay a lot of contractors to move paper from point A to point B (finding reliable people dumb/crazy enough to work 7 days a week, driving in any weather, with no vacations can be tough, too) and gas is very expensive these days. It's frankly not very economically smart for the publisher (who either needs to have a distribution contract with somebody else or their own distribution infrastructure), the distributor, or the carriers.
"These pages aren't generated by an XSLT transformation from XML to HTML (and if they were, they certainly wouldn't be using a.xml handler in the doctype or URI handling)."
This is handled via AxKit for gentoo.org.
I disagree. The *bad* thing about wikis is that they're open. In a wonderful world where people were smart, it'd be great. Unfortunately, the reality is that wikis tend to be filled with garbage by every moron and their mother who thinks they can write. The only way to keep them usable is to have a pretty massive number of dedicated contributors who run around rechecking everything all the time to make sure nobody fucked it up.
In fact, in just the last couple hours while I was watching a movie, I noticed a few pages on the Linuxquestions.org wiki go from thought out, clean, well-written copy to total garbage. I could sit here and take a bunch of time that could otherwise be spent productively and fix it up and wait for the next idiot to make a dumb change, but it'd be almost as futile as reading Slashdot.
Yeah. The problem was that a bunch of not particularly bright individuals apparently didn't check the date and pitched a fit.
Which was fucking stupid.
AMD64 refers to the architecture (formerly x86-64).
The two chips are the Athlon64 (desktops and notebooks) and the Opteron (workstations and servers -- mostly SMP-land). The Opteron (besides doing SMP, at least if you have a 2xx, 4xx, or 8xx) has more memory bandwidth.
The current Athlon64 FX-51 is pretty much an Opteron 1xx.
Actually this has been in the works (except just signing the Manifests - which is why Manifests were created) but hasn't had enough push behind it to actually finish the important implementation details
The source code is only available via BitKeeper, as far as I can tell from their site. The BitKeeper tools are not free software and cannot be used by anyone who has contributed to a competing product, according to the license for the free-as-in-beer version of BitKeeper.
Is there somewhere else to get source and I'm just missing it?
I didn't see anyone mention this, but in addition to service dependencies, we also already have parallel functionality.
Put RC_PARALLEL_STARTUP="yes" in/etc/conf.d/rc.
We already sell t-shirts and other stuff in our cafepress store.
I already said we're going nonprofit. What else can we do right now? We need the donations to continue to operate. We understand your concerns and are going nonprofit.
1. See the new management proposal which fixes this problem.
2. See the new management proposal which mentions our commitment to going nonprofit (as do -dev mails from the past). Last I heard, the plan is to have a board for the nonprofit who vote.
3. There is hardly any secrecy. Currently, there is -core, which is only closed because it's where we discuss serious security vulnerabilities that package maintainers have asked us not to disclose until they have a fix out. Development matters are either wholly on -dev (which is public) or crossposted between -core and -dev to make sure everyone sees it. All development effort is discussed on -dev; in fact, the only -core-only mails recently have been people announcing they're going on vacation...
When have we ever tried to pass ourselves off as a nonprofit?
We're currently a for-profit. We're going nonprofit soon. We've always been upfront about our current situation.
We're not making any money, by the way.
Actually we're going nonprofit soon. This has been repeatedly mentioned on the gentoo-dev mailing list by drobbins.
Re:former dev speaks out on Gentoo and its FUD
on
Gentoo Games
·
· Score: 1
Sure, if this was actually about the business rather than about your personal problems with Daniel.
Re:former dev speaks out on Gentoo and its FUD
on
Gentoo Games
·
· Score: 1
The work done was all copyright Gentoo Technologies. That means that copyright ownership was transferred to Gentoo. Regardless of what's ethical and what isn't, it's all legal.
I'm not commenting on any of the more personal aspects. We can talk about that privately if you want to email me. It doesn't belong here.
Re:former dev speaks out on Gentoo and its FUD
on
Gentoo Games
·
· Score: 1
Yes, I know who you are.
Note that I didn't comment on any of the personal stuff, only the factually incorrect parts that apply to Gentoo as a whole in a technical sense.
Re:former dev speaks out on Gentoo and its FUD
on
Gentoo Games
·
· Score: 1
IANAL, but I don't see anything in the GPL requiring credits. Regardless of that, the LiveCD has been entirely reworked for 1.4rc3 and newer.
1.4 final is delayed because it's not ready. I could build a few stages and throw them up as 1.4 right now if that's what people want - if people want a complete, finished product, with a full set of stages for all CPU types and a bug-free LiveCD, they need to wait.
Re:I love Gentoo, but...
on
Gentoo Games
·
· Score: 1
Because if we released right now, it'd be incomplete, mainly. I'm planning to start the release process for 1.4 towards the end of the month.
Slashdot Mirror
Eh, I can assure you it's not just the 10-14 year olds out of a job when print media dies (and it will, but probably not real soon).
:)
I deliver newspapers (motor route, 50 miles, ~250 papers total run -- a relatively small route) seven days a week and I guarantee I'm well out of the 10-14 age range. Most carriers out this way (rural New Hampshire) are at least 30+ -- a few are _much_ older folks (75+) contracting to supplement social security payouts who probably won't live long enough to be out of a job when it comes right down to it.
I can't disagree that the death of print media is a Good Thing, though. Frankly, production-related issues (web is faster, trees are good, etc...) are not nearly as important as two very immediate issues: you have to pay a lot of contractors to move paper from point A to point B (finding reliable people dumb/crazy enough to work 7 days a week, driving in any weather, with no vacations can be tough, too) and gas is very expensive these days. It's frankly not very economically smart for the publisher (who either needs to have a distribution contract with somebody else or their own distribution infrastructure), the distributor, or the carriers.
I'll kill another living animal for fun and claim it's for fun. :)
My conclusions are quite alarming, suggesting that 99.9% of Slashdot story summaries are retardedly inaccurate.
"These pages aren't generated by an XSLT transformation from XML to HTML (and if they were, they certainly wouldn't be using a .xml handler in the doctype or URI handling)."
This is handled via AxKit for gentoo.org.
I disagree. The *bad* thing about wikis is that they're open. In a wonderful world where people were smart, it'd be great. Unfortunately, the reality is that wikis tend to be filled with garbage by every moron and their mother who thinks they can write. The only way to keep them usable is to have a pretty massive number of dedicated contributors who run around rechecking everything all the time to make sure nobody fucked it up. In fact, in just the last couple hours while I was watching a movie, I noticed a few pages on the Linuxquestions.org wiki go from thought out, clean, well-written copy to total garbage. I could sit here and take a bunch of time that could otherwise be spent productively and fix it up and wait for the next idiot to make a dumb change, but it'd be almost as futile as reading Slashdot.
Recent baselayouts have udev support if you want it.
Yeah. The problem was that a bunch of not particularly bright individuals apparently didn't check the date and pitched a fit. Which was fucking stupid.
AMD64 refers to the architecture (formerly x86-64). The two chips are the Athlon64 (desktops and notebooks) and the Opteron (workstations and servers -- mostly SMP-land). The Opteron (besides doing SMP, at least if you have a 2xx, 4xx, or 8xx) has more memory bandwidth. The current Athlon64 FX-51 is pretty much an Opteron 1xx.
Actually there are Silicon Image drivers that support that chipset emerging now for the 2.6 kernel
Is it worth getting _any_ machine without planning to use Linux?
Actually this has been in the works (except just signing the Manifests - which is why Manifests were created) but hasn't had enough push behind it to actually finish the important implementation details
The source code is only available via BitKeeper, as far as I can tell from their site. The BitKeeper tools are not free software and cannot be used by anyone who has contributed to a competing product, according to the license for the free-as-in-beer version of BitKeeper. Is there somewhere else to get source and I'm just missing it?
I didn't see anyone mention this, but in addition to service dependencies, we also already have parallel functionality. Put RC_PARALLEL_STARTUP="yes" in /etc/conf.d/rc.
We already sell t-shirts and other stuff in our cafepress store. I already said we're going nonprofit. What else can we do right now? We need the donations to continue to operate. We understand your concerns and are going nonprofit.
1. See the new management proposal which fixes this problem. 2. See the new management proposal which mentions our commitment to going nonprofit (as do -dev mails from the past). Last I heard, the plan is to have a board for the nonprofit who vote. 3. There is hardly any secrecy. Currently, there is -core, which is only closed because it's where we discuss serious security vulnerabilities that package maintainers have asked us not to disclose until they have a fix out. Development matters are either wholly on -dev (which is public) or crossposted between -core and -dev to make sure everyone sees it. All development effort is discussed on -dev; in fact, the only -core-only mails recently have been people announcing they're going on vacation...
Give it a rest, Gerk. The troll routine is getting old.
They were loaned and we are returning them to him.
When have we ever tried to pass ourselves off as a nonprofit? We're currently a for-profit. We're going nonprofit soon. We've always been upfront about our current situation. We're not making any money, by the way.
Actually we're going nonprofit soon. This has been repeatedly mentioned on the gentoo-dev mailing list by drobbins.
Sure, if this was actually about the business rather than about your personal problems with Daniel.
The work done was all copyright Gentoo Technologies. That means that copyright ownership was transferred to Gentoo. Regardless of what's ethical and what isn't, it's all legal. I'm not commenting on any of the more personal aspects. We can talk about that privately if you want to email me. It doesn't belong here.
Yes, I know who you are. Note that I didn't comment on any of the personal stuff, only the factually incorrect parts that apply to Gentoo as a whole in a technical sense.
IANAL, but I don't see anything in the GPL requiring credits. Regardless of that, the LiveCD has been entirely reworked for 1.4rc3 and newer. 1.4 final is delayed because it's not ready. I could build a few stages and throw them up as 1.4 right now if that's what people want - if people want a complete, finished product, with a full set of stages for all CPU types and a bug-free LiveCD, they need to wait.
Because if we released right now, it'd be incomplete, mainly. I'm planning to start the release process for 1.4 towards the end of the month.