I mean, seriously -- I use Fedora for development at work, and it's a joke. The desktop is slow and unresponsive, and installation of new programs is a pain in the ass.
You're obviously using a different FC3 to me then. I've been using it for... wait for it... development almost constantly since it came out, and haven't had any such problems.
I had to install the trial of Rational Rose Modeller the other day, and it was a sad experience. I had to manually create a shortcut to/opt/IBM/blah/blah/blah/whocares in order to even be able to use it from the interface.
Okay... you're complaining that a 3rd party vendor can't be bothered to package their software correctly, and that's somehow Red Hat's fault? Please. That's like saying that because some random Windows program installs itself to C:/Foo/Bar/Baz/139548754/ and then doesn't create Start Menu shortcuts, it's Microsoft's fault.
..like the business of not storing deltas to files
Actually, that's a feature. One of Linus' main objections to existing SCMs was that they're too slow -- and most of that sluggishness comes from the time necessary to calculate and resolve deltas in the ubiquitous RCS files.
As far as I can tell, it's actually working pretty well so far.
- random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronounciation of "get" may or may not be relevant. - stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang. - "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room. - "goddamn idiotic truckload of sh*t": when it breaks
The DTN isn't a link-level protocol -- perhaps the Licklider Transmission Protocol (linked from DTNRG site) fulfils the needs (although that's designed more for v. long latency RF links).
It could just be you've stumbled across a problem no-one's looked at.
I think the RIAA, MIAA and friends are fighting a battle that they'll inevitably lose, no matter how expertly they play the governmental and legal systems.
I went for a job interview at Snell & Wilcox (Google it) and they showed me a huge rack. They said, "This is a realtime HDTV compositing platform." I said, "That's a bit big, isn't it?" They said, "Yes, but it needs to be this big. It has 128 GB of RAM in it, because content producers need to mix in segments up to four minutes."
With assinine "agreements" (like if they did give you the choice...) like that that bind the hands of their customers, it's not wonder that they go down the drain!!!
What, you mean like Microsoft, Adobe and MacroMedia? Their agreements are a lot worse, and they seem to be doing fine...
That's why I compile a toolchain myself, chroot to it, and then build enough of Linux to compile. Once this is done, I install it by hand into the correct directories, reboot, and build everything from source. This way I get a complete system whithout all that "emerge" bullshit.
Yeah, that's the way I do it. Works really well for me!
I doubt that lack of heat to keep the gas pressure up is going to be a problem.
Don't forget that on Earth things cool quickly by evaporative cooling, conduction or convection. In space, the only way to lose heat from a habitat would be by radiation. Once you've got a crew (human bodies generate large amounts of heat), life support systems, cooking facilities and lights, the real problem is going to be how to get rid of heat.
Everything I've seen under linux is backend server stuff; not really the best set up for 6th graders learning the nuts and bolts.
The first database software I used - well before I started high school - was MySQL. On Windows. Call me wierd, but I didn't find it hard to learn the nuts and bolts of that at all. MySQL is quite well documented.
Then again, I suppose I was quite a bit more motivated than your run-of-the-mill high-schooler is.
IMHO, the best way to teach people to use a database is via the backend-to-a-website route. Get them to make a website, and then keep asking them to add/remove/update pages. They'll soon be begging to be taught to add a database backend
The 16-bit prefix FFFF is the IPv6 compatibility subnet for IPv4.
HTH.
You're obviously using a different FC3 to me then. I've been using it for... wait for it... development almost constantly since it came out, and haven't had any such problems.
Okay... you're complaining that a 3rd party vendor can't be bothered to package their software correctly, and that's somehow Red Hat's fault? Please. That's like saying that because some random Windows program installs itself to C:/Foo/Bar/Baz/139548754/ and then doesn't create Start Menu shortcuts, it's Microsoft's fault.
Funny, that's exactly what I've got on my Sharp Zaurus C-3000.
Which has a 4 GB hard drive, and *actually* runs Linux, unlike the unit under discussion.
Ah, you mean exactly like GNOME does!
For what it's worth (I read the mailing list):
The full OGP core will fill most of the XC3S4000 (that's the second largest FPGA in the Spartan-3 product line).
Sure, you'd probably be able to make a *2D* core fit into a tiny FPGA, but a full OpenGL shader pipeline? Not likely.
And yes, I program FPGAs for a living at the moment.
...because if you're running something other than Solaris/Linux/Windows on a x86{,-64} or Sparc box, 80% of the Java software out there won't work.
Whereas the *full* Python VM is available for just about *every* platform I can think of right now.
git license is in the COPYING file. git-pasky (the interface scripts that actually do stuff) license is also in the COPYING file. They're both GPLv2.
Actually, that's a feature. One of Linus' main objections to existing SCMs was that they're too slow -- and most of that sluggishness comes from the time necessary to calculate and resolve deltas in the ubiquitous RCS files.
As far as I can tell, it's actually working pretty well so far.
Yes, that's right; from the git README:
The DTN isn't a link-level protocol -- perhaps the Licklider Transmission Protocol (linked from DTNRG site) fulfils the needs (although that's designed more for v. long latency RF links).
It could just be you've stumbled across a problem no-one's looked at.
...which is already being researched by the NASA and the IETF: more info.
See this paper.
Give me a board with two HDCP connectors, an FPGA and a USB port and I'll spoof any commercial HDCP display in a day or two.
...uses a dual-CPU G5 exclusively nowadays.
Among a large number of other people.
...when I see that six of the "Top Downloads" on Sourceforge's front page are P2P clients.
I think the RIAA, MIAA and friends are fighting a battle that they'll inevitably lose, no matter how expertly they play the governmental and legal systems.
King Canute didn't have much luck either.
32 GB = ~ 1 minute HDTV
I went for a job interview at Snell & Wilcox (Google it) and they showed me a huge rack. They said, "This is a realtime HDTV compositing platform." I said, "That's a bit big, isn't it?" They said, "Yes, but it needs to be this big. It has 128 GB of RAM in it, because content producers need to mix in segments up to four minutes."
At which point my jaw hit the floor.
Alan Cox has applied the patches to his tree: Google linux.kernel archive.
So maybe being obnoxious has got GRSecurity some attention.
Yeah, that's the way I do it. Works really well for me!
Oh, wait...
I doubt that lack of heat to keep the gas pressure up is going to be a problem.
Don't forget that on Earth things cool quickly by evaporative cooling, conduction or convection. In space, the only way to lose heat from a habitat would be by radiation. Once you've got a crew (human bodies generate large amounts of heat), life support systems, cooking facilities and lights, the real problem is going to be how to get rid of heat.
The first database software I used - well before I started high school - was MySQL. On Windows. Call me wierd, but I didn't find it hard to learn the nuts and bolts of that at all. MySQL is quite well documented.
Then again, I suppose I was quite a bit more motivated than your run-of-the-mill high-schooler is.
IMHO, the best way to teach people to use a database is via the backend-to-a-website route. Get them to make a website, and then keep asking them to add/remove/update pages. They'll soon be begging to be taught to add a database backend
> If you ever feel especially masochistic, check out Linux From Scratch.
You don't need to be masochistic.
I use an LFS system on my Sharp laptop. It's really not hard to install, and as long as you can configure a kernel, you're fine.
I managed to get my LFS system up and running with very little prior Unix experience (and a large dose of perseverence).
The only bad thing was the long time needed to compile some of the applications. OO.org took 23 hours.
He's being facetious... he's being OTT and silly to emphasise his point? Jeez, haven't you heard of dark humour before?
"I'd also recommend that you don't feed your computer." If I don't feed mine I get: +++ OUT OF CHEESE ERROR +++ Has anyone else had the same problem?
...I'm getting a job as an usher right now.