The multimedia capabilities of BeOS are excellent, and the hardware requirements are a lot lower than you would expect. Install BeOS on your Mini-ITX based box, and you will have yourself the beginnings of a Home Theater PC.
Re:I've used genetic algorithms
on
Digital Darwin
·
· Score: 1
I work from home, and have a network of 5 PCs of various specifications. You can tell when they are on because the floorboards in the hall vibrate, never mind the noise they make.
I have recently invested in a VIA EPIA-M10000 motherboard. It is very, very quiet.
Sure, it isn't as fast as the latest P4 or Athlon, but it plays DVD (with hardware support), DivX, and MP3 media without any problems. Quake 3 runs well.
More importantly, I can run all my business applications without any noticable loss in speed.
I'm going to ditch my other boxes and buy some more of these EPIA systems. It's the quiet life for me.
Linux From Scratch [linuxfromscratch.org] is not a disto, but a set of instructions for building a GNU/Linux system from little more than an existing distro. The Beyond Linux From Scratch [linuxfromscratch.org] project builds on this tradition, providing instructions for installing a number of other packages.
Having said that, I would recommend that anyone serious about furthering their knowledge of Linux, and at least 750MB of free hard disk space should give it a go. I got into Linux back in '93, and knew quite a lot. Then I stumbled across Linux From Scratch (LFS) - I didn't realise how much I didn't know until finishing my first complete build.
I now run an number of LFS-based systems at home and at work, and have never looked back.
BTW, I am typing this on my Gentoo [gentoo.org], 1.4_rc4 build.:-)
I guess that is what heppens when open source gets good. Is this a direct response to the popularity of SDL? [www.libsdl.org] Will we see more and more companies (L)GPL'ing their code just to compete with the open source alternatives?
When I first started to use open source software (back in '93), I always wondered how easy it would be to release compromised sources, whether intentionally or not.
Once I got into it, hey, I trusted these guys. They were the good guys. We were the good guys. The community was built on trust, and it worked.
We used to scoff when we heard about the torjans in the latest version of Microsoft Word. That would never happen to us... unless they sorted that WINE [wine.org] project out.;-)
Now we face the same issues. As source distributions (I'm not discounting binary distributions - if you trust RedHat, that's your call) increase in popularity, this will become more of a problem.
We need to tighten up the procedures that we use. We need to ensure that the software we put out is the software that the users download and use. We need to ensure that nobody can comprimise our systems in this way.
That's good if you can assure that the MD5 checksum is for the original tarball. What if the guy who placed the torjan placed a new MD5 checksum as well?
At the bottom of the article is a link [news.com] which describe viral payloads being transmitted via jpeg images. One of the problems is that the payload is visible because it corrupts the image. Not any more...
...without a cool name like Google.
I searched on my name, and found nothing of interest. I tried with Google, and I'm third link from the top! Way to go.
IBM got screwed by Microsoft when they partnered with them to produce OS/2. Microsoft jumped ship and produced Windows NT, leaving IBM with a lame duck (although a technically brilliant dead duck). That's what Microsoft does with partnering and source code sharing.
IBM, release the source code to OS/2...
I see there being two camps - those that want an OS that looks like Microsoft Windows and those that want something different.
One of the reasons that I moved to GNU/Linux was that I prefered it to Windows. I choose GNOME because it gives me something new and exciting. I enjoy using the desktop. But I'm sure that there are others who enjoy KDE in the same way.
Commercially, KDE makes sense. Businesses want something their users know (and possibly love?) So KDE tries to be a better Windows than Windows. But then I think that this is missing the point. If everyone wants a desktop that looks like Windows, why not give them Windows? Why bother re-inventing the wheel? Why not invent something that will make the wheel obsolete?
What worries me is that if we can only immitate, how can we ever innovate?
I don't remember Alan being special, but he was certainly different.
I remember one dark evening in the Junior Common Room at Swansea University (later, JC's) supping beer and discussing the merits of C file locking in developing a MUD for Pyramid.
When he spoke about the language, he really knew what he was talking about. Alan filled me with a passion for C, although I doubt he knows it.
Slashdot Mirror
Still trying to figure out why you'd use BeOS.
The multimedia capabilities of BeOS are excellent, and the hardware requirements are a lot lower than you would expect. Install BeOS on your Mini-ITX based box, and you will have yourself the beginnings of a Home Theater PC.
So how many lines of code are you compiled from?
I work from home, and have a network of 5 PCs of various specifications. You can tell when they are on because the floorboards in the hall vibrate, never mind the noise they make.
I have recently invested in a VIA EPIA-M10000 motherboard. It is very, very quiet.
Sure, it isn't as fast as the latest P4 or Athlon, but it plays DVD (with hardware support), DivX, and MP3 media without any problems. Quake 3 runs well.
More importantly, I can run all my business applications without any noticable loss in speed.
I'm going to ditch my other boxes and buy some more of these EPIA systems. It's the quiet life for me.
Why compare apples with apples? Why not apples with pcs? After all, the Athlon is built around the x86 architecture... :-P
Provided that the life form in question is carefully organised into petri-dishes, hematically sealed in a selection of jars, and stored in a locker.
Linux From Scratch [linuxfromscratch.org] is not a disto, but a set of instructions for building a GNU/Linux system from little more than an existing distro. The Beyond Linux From Scratch [linuxfromscratch.org] project builds on this tradition, providing instructions for installing a number of other packages.
:-)
Having said that, I would recommend that anyone serious about furthering their knowledge of Linux, and at least 750MB of free hard disk space should give it a go. I got into Linux back in '93, and knew quite a lot. Then I stumbled across Linux From Scratch (LFS) - I didn't realise how much I didn't know until finishing my first complete build.
I now run an number of LFS-based systems at home and at work, and have never looked back.
BTW, I am typing this on my Gentoo [gentoo.org], 1.4_rc4 build.
I guess that is what heppens when open source gets good. Is this a direct response to the popularity of SDL? [www.libsdl.org] Will we see more and more companies (L)GPL'ing their code just to compete with the open source alternatives?
Using the power grid for internet access is a great idea, provided that they don't later claim prior art on the use of sockets.
When Profiling Goes Wrong [/.]
When I first started to use open source software (back in '93), I always wondered how easy it would be to release compromised sources, whether intentionally or not.
Once I got into it, hey, I trusted these guys. They were the good guys. We were the good guys. The community was built on trust, and it worked.
We used to scoff when we heard about the torjans in the latest version of Microsoft Word. That would never happen to us... unless they sorted that WINE [wine.org] project out. ;-)
Now we face the same issues. As source distributions (I'm not discounting binary distributions - if you trust RedHat, that's your call) increase in popularity, this will become more of a problem.
We need to tighten up the procedures that we use. We need to ensure that the software we put out is the software that the users download and use. We need to ensure that nobody can comprimise our systems in this way.
Take a look at tcpdump.org. There are no MD5 checksums for any of the tarballs. Doesn't change my last comment, though. :-)
That's good if you can assure that the MD5 checksum is for the original tarball. What if the guy who placed the torjan placed a new MD5 checksum as well?
At the bottom of the article is a link [news.com] which describe viral payloads being transmitted via jpeg images. One of the problems is that the payload is visible because it corrupts the image. Not any more...
Er... you mean fvwm?
I don't know about Delphi, but most of our code is developed in Delhi.
If you're single. Now your wife will know that you are in the pub, because she was emailed when you entered. :-)
I thought they just took other peoples worked and patched it?
...without a cool name like Google. I searched on my name, and found nothing of interest. I tried with Google, and I'm third link from the top! Way to go.
IBM got screwed by Microsoft when they partnered with them to produce OS/2. Microsoft jumped ship and produced Windows NT, leaving IBM with a lame duck (although a technically brilliant dead duck). That's what Microsoft does with partnering and source code sharing. IBM, release the source code to OS/2...
This is so wrong, it is stupid. And I ask: how much of this 'tax' will actually make it to the authors/artists/song writers/etc?
Bet they use WINE. Now that will make me smile. :-)
One of the reasons that I moved to GNU/Linux was that I prefered it to Windows. I choose GNOME because it gives me something new and exciting. I enjoy using the desktop. But I'm sure that there are others who enjoy KDE in the same way.
Commercially, KDE makes sense. Businesses want something their users know (and possibly love?) So KDE tries to be a better Windows than Windows. But then I think that this is missing the point. If everyone wants a desktop that looks like Windows, why not give them Windows? Why bother re-inventing the wheel? Why not invent something that will make the wheel obsolete?
What worries me is that if we can only immitate, how can we ever innovate?
I don't remember Alan being special, but he was certainly different.
I remember one dark evening in the Junior Common Room at Swansea University (later, JC's) supping beer and discussing the merits of C file locking in developing a MUD for Pyramid.
When he spoke about the language, he really knew what he was talking about. Alan filled me with a passion for C, although I doubt he knows it.
Cheers Alan...