Have you ever checked out PCGamer and PCGamer UK? The UK version reads like it was written by 12 year olds. How about an intelligent, insightful gaming magazine? An Economist of gaming, anyone?
I saw a couple presentations on this rover... yeah, it's supposed to be cheap, small, and light. They could drop 10s, 100s of these things, so if one gets stuck in a weird (and presumably interesting) spot, it just gets to analyze that spot until it dies or it gets blown out again.
Their current plan is that if it gets stuck, then it becomes a "stationary sensor" (which could be valuable as well). These things would be cheap, light, and small... you could drop 50 of them. So if a few get stuck in weird places, it won't do any harm. And you get to study those weird places for a long time.
My take on this is that he's not talking about a new kind of distribution; he's talking about a central repository. Look at CPAN. It's not a "Perl distribution", it's a central repository of software that can be applied to an existing Perl installation.
Similarly with this Componentized Linux idea (or my idea, if I have it wrong). You'd have a central repository of software (linux.com, linuxsoftware.com, packages.com, whatever). The individual users would download a core from a distribution or a provider, or whatever (like they do with Perl), then they would go through a wizard, choosing the various things they want (KDE, X, Apache, Mozilla).
The components would then be downloaded from the central 'official' repository, customized (if needed) for your specific core, and installed easily.
The result is that there wouldn't need to be a duplication of packaging effort and hosting bandwidth for each distribution out there. All distributions would use one repository, call it the Central Linux Software Repository (CLSR) or something. New software would uploaded to that, and thus be available instantly to all Linux users.
I don't remember my first MP3, but I remember downloading Napster way back when it first came out because of some article in PC WORLD or something. I ran it once, didn't know what the hell it was for, and uninstalled it until I became enlightened a couple years later.
Interesting. But that's an estimate for a round-trip with no stop-over. I assume that once they get there, they'll be spending some time, which would tack on extra radiation. How 'bout it?
"A round trip to Mars would be of a different order of magnitude. Brookhaven puts the exposure at 130,000 millirem over two and a half years. That is equivalent to almost 400 years of natural exposure."
General conclusion: Nobody knows how that much radiation will affect a Mars mission.
According to articles I've read, the problem with going to Mars is radiation. There's much more out there then in LEO, and they'll be out there for longer. Which means we need to do experiments on how to keep people healthy for long durations in space, from radiation and the effects of weightlessness. So we need the ISS. It's either that, or shoot a few astronauts to Mars just to find out they can't walk when they get there.
I've thought about this, too. It seems like a blatently hypocritical policy. On the one hand, you have game EULAs that allow you to make a backup copy. At the same time, you have copyright protection schemes that try to prevent you from making that copy. This seems like something the courts could take up, honestly...
In the end, though, the effect is to shut out casual copiers (i.e. legit backups) while doing nothing to hinder the truly dedicated (who will used cracks and stuff anyway).
Does anyone have a copy of the Raven Shield EULA around? What does it say about backup copies?
I have mine as a mix of tasks and apps. Desktop 1 has non-serious stuff (e-mail, 'net radio, etc.), while Desktops 2-4 have work-related stuff. I'm writing documentation, so Desk 2 has my app, Desk 3 has my doc, and Desk 4 has Photoshop for screenshooting.
Here's my 2c about the whole package-management thing:
- apt/dpkg is good. I should be able to type 'apt-get install mozilla' and magically have Mozilla.
- Dependencies should be satisfied not by package names (mozilla vs. mozilla-browser vs. mozilla1.5 vs. whatever), but by actual dependencies (Mozilla needs GTK 2.0. apt searches for libgtk.so.2.0.0. If it's there, dependency has been satisfied.)
- The entire problem with the download-and-double-click thing with Debian is that other people don't distribute.debs. If.deb was a standard, and it could be installed through an apt front-end by double-clicking it, this point is moot.
- apt/dpkg should have a seamless binary/source option, combining the good points of Gentoo and Debian. Why not have an/etc/make.conf in Debian that is referenced when you type `apt --source install mozilla` or whatever?
Well, he's right. I realize there's Sid to fall back on, but the question here is of support. Sid isn't "supported", it's just there in case people want to try it out. The official Debian line is that nobody should be using Sid from day to day anyway. To get a true, supported Debian system, you need to use Woody, and that's painful.
The world would be a perfect place if Debian released packages on Gentoo's schedule.
I've seen a lot of comments about how open source developers don't get paid, so they don't have any incentive to fix a certain feature or make a package easier to use.
Enter OpenSourceXperts.com, similier to Gnome's recent bounty hunt. Some people are willing to pay money for a feature, others are willing to develop it for that money. This place hooks 'em up.
Slashdot Mirror
Well, if anyone's interested in helping out, the XFree86 nv driver needs a few good developers.
Have you ever checked out PCGamer and PCGamer UK? The UK version reads like it was written by 12 year olds. How about an intelligent, insightful gaming magazine? An Economist of gaming, anyone?
I saw a couple presentations on this rover... yeah, it's supposed to be cheap, small, and light. They could drop 10s, 100s of these things, so if one gets stuck in a weird (and presumably interesting) spot, it just gets to analyze that spot until it dies or it gets blown out again.
Their current plan is that if it gets stuck, then it becomes a "stationary sensor" (which could be valuable as well). These things would be cheap, light, and small... you could drop 50 of them. So if a few get stuck in weird places, it won't do any harm. And you get to study those weird places for a long time.
Sign the petition to bring PlanetSide to Linux:
http://petitiononline.com/pslinux/petition.html
My take on this is that he's not talking about a new kind of distribution; he's talking about a central repository. Look at CPAN. It's not a "Perl distribution", it's a central repository of software that can be applied to an existing Perl installation.
Similarly with this Componentized Linux idea (or my idea, if I have it wrong). You'd have a central repository of software (linux.com, linuxsoftware.com, packages.com, whatever). The individual users would download a core from a distribution or a provider, or whatever (like they do with Perl), then they would go through a wizard, choosing the various things they want (KDE, X, Apache, Mozilla).
The components would then be downloaded from the central 'official' repository, customized (if needed) for your specific core, and installed easily.
The result is that there wouldn't need to be a duplication of packaging effort and hosting bandwidth for each distribution out there. All distributions would use one repository, call it the Central Linux Software Repository (CLSR) or something. New software would uploaded to that, and thus be available instantly to all Linux users.
It's a completely different paradigm.
You dig?
How?
How do I tell Debian to download VIM, apply my compile optimization flags and optional components, compile the package, and install it?
This is a serious question, I've been looking for a way to do this.
Foomatic. I still don't know what the hell it does, just cause I can't get passed the name.
I don't remember my first MP3, but I remember downloading Napster way back when it first came out because of some article in PC WORLD or something. I ran it once, didn't know what the hell it was for, and uninstalled it until I became enlightened a couple years later.
This museum is the Air Force Museum in Dayton, Ohio. It's an amazing place, I suggest you check it out.
Murder boosts gun sales! Help support Smith & Wesson! Kill people!
Yeah, and more teens drink alcohol than do other drugs. Lies, damn lies, and statistics.
Interesting. But that's an estimate for a round-trip with no stop-over. I assume that once they get there, they'll be spending some time, which would tack on extra radiation. How 'bout it?
Actually, that's not true. See this NYT story.
I quote:
"A round trip to Mars would be of a different order of magnitude. Brookhaven puts the exposure at 130,000 millirem over two and a half years. That is equivalent to almost 400 years of natural exposure."
General conclusion: Nobody knows how that much radiation will affect a Mars mission.
According to articles I've read, the problem with going to Mars is radiation. There's much more out there then in LEO, and they'll be out there for longer. Which means we need to do experiments on how to keep people healthy for long durations in space, from radiation and the effects of weightlessness. So we need the ISS. It's either that, or shoot a few astronauts to Mars just to find out they can't walk when they get there.
Mod parent up.
I've thought about this, too. It seems like a blatently hypocritical policy. On the one hand, you have game EULAs that allow you to make a backup copy. At the same time, you have copyright protection schemes that try to prevent you from making that copy. This seems like something the courts could take up, honestly...
In the end, though, the effect is to shut out casual copiers (i.e. legit backups) while doing nothing to hinder the truly dedicated (who will used cracks and stuff anyway).
Does anyone have a copy of the Raven Shield EULA around? What does it say about backup copies?
Can Evolution import my Mozilla Mail yet? I've tried the (ancient) Debian Woody version, and that feature wasn't available.
I have mine as a mix of tasks and apps. Desktop 1 has non-serious stuff (e-mail, 'net radio, etc.), while Desktops 2-4 have work-related stuff. I'm writing documentation, so Desk 2 has my app, Desk 3 has my doc, and Desk 4 has Photoshop for screenshooting.
Here's my 2c about the whole package-management thing:
.debs. If .deb was a standard, and it could be installed through an apt front-end by double-clicking it, this point is moot.
/etc/make.conf in Debian that is referenced when you type `apt --source install mozilla` or whatever?
- apt/dpkg is good. I should be able to type 'apt-get install mozilla' and magically have Mozilla.
- Dependencies should be satisfied not by package names (mozilla vs. mozilla-browser vs. mozilla1.5 vs. whatever), but by actual dependencies (Mozilla needs GTK 2.0. apt searches for libgtk.so.2.0.0. If it's there, dependency has been satisfied.)
- The entire problem with the download-and-double-click thing with Debian is that other people don't distribute
- apt/dpkg should have a seamless binary/source option, combining the good points of Gentoo and Debian. Why not have an
--
Joel
Well, he's right. I realize there's Sid to fall back on, but the question here is of support. Sid isn't "supported", it's just there in case people want to try it out. The official Debian line is that nobody should be using Sid from day to day anyway. To get a true, supported Debian system, you need to use Woody, and that's painful.
The world would be a perfect place if Debian released packages on Gentoo's schedule.
Try opensourcexperts.com. They do exactly what you were talking about.
I submitted a feature request to Bugzilla to allow bounties within bug reports.
Dammit, that link was http://opensourcexperts.com.
I've seen a lot of comments about how open source developers don't get paid, so they don't have any incentive to fix a certain feature or make a package easier to use.
Enter OpenSourceXperts.com, similier to Gnome's recent bounty hunt. Some people are willing to pay money for a feature, others are willing to develop it for that money. This place hooks 'em up.