"Tiny window 1/8 screen in size, fonts that ugly that I did not even know that they existed on my box"
Do you have your server resolution (dpi) set right. Mozilla is one of many new (like GIMP 1.2, Konsole 1.1.x) X Windows apps that require your dpi to be set right. On my X Server (Xpmac) that is done using: 'Xpmac -dpi 72' -- other X Servers do this differently. Fonts will look really large in these apps if your DPI is too high, and really small if your DPI is too low. If you are getting blocky fonts then for some reason your truetype or ghostscript fonts weren't set up right.
"buttons and widgets coming from a nightmare..."
You don't like the new XUL? Well, guess what it's really themeable. see Mozillazine for details. Some of the nightly builds (at least for Win32) have an option that caches the widgit pixmaps so they are as fast as your reguluar ones. They will be fast really soon, according to Mozillazine.:)
And yes, Netscape 4.7 works good for me (it's stable and has only minor memory leaks that all web browsers have), I am using it now -- but I would like to be able to upgrade someday.
*Are you running with a frame buffer native to your card instead of the generic OpenFirmware one? That means running without using video=ofonly or No Video Driver Checked. Most Macs use atyfb, controlfb, aty128fb, or valykriefb -- most likely on a PowerBook G3 it's atyfb.
*Check out the new Xpmac and XFree86-3.3.5. Get the new Xpmac from http://khendricks.ivey.uwo.ca/rage128_us b/. Don't forget if you have a ATI Mach64 video card to start it with 'Xpmac -mach64', you will get much better preformance.
A few things to check before claiming PPC Linux has really slow video:
Are you running with video=ofonly or No Video Driver Checked? Both of those options will make your video much slower.
If you have a Macintosh with a Rage128 card, do you have the new accelorated XF68_FBDev or Kevin Hendrick's new Xpmac? If not, it could slow you down.
You may want to try out Kevin Hendrick's new version of Xpmac. It is signicantly faster then XF68_FBDev on my machine with a Mach64 card. Don't forget to use Xpmac with the -mach64 argument or you won't get the acceloration.
In my experience Xpmac -mach64 is as fast or faster then Mac OS running at 1024x768 @ thousands of colors. Then again, on my 2 meg ATI Mach64, that doesn't take much.
I have to agree with the Macintosh version of Microsoft Internet Exploiter is slow and crashy. It also has problems rendering pages that Netscape 4.5.1 (the version I run -- and prefer 'cause it's really stable) renders perfectly.
Most people I know who use Macs still prefer Netscape Communicator, and I do, because it's just a great browser. Pluse there is a PowerPC Linux version of Netscape Communicator. For us that run both PowerPC Linux and Mac OS, having the same browser and interface is a blessing.
I can't comment on doing this digitally, since I haven't worked with really expensive CD-ROM drives, although ALL computer CD-ROM drives are capable of doing it the old fashion way (digital to analog to digital type setup). This isn't the best for sound quality, but in most cases it perfectly fine for everyday -- and is how most Mp3s are ripped and most CD-ROM drives. So basically the analog audio out cable of the CD-Drive hooks to a special analog input on the motherboard.
On newer PowerMacs (G4s come to mind) I have heard that this is completely digital (a PCM digital cable hooks to motherboard directly), so you don't get any sound degration at all from the decoding and reincoding and redecoding of the music.
Why they don't just use standard ATAPI or SCSI for digitally encoded sound data is beyond me. Maybe because it takes up to much bandwidth on slower buses? Or maybe because the CD player would stop playing (or play static) when you were transfering lots of data this way?
Again, I have only messed with PowerPC-based PowerMacs, so I don't know how PCs do this.
However, I don't think it's true. For one why would one desktop enviroment want to kill another one? There is no money reward.
And I have yet to find an example of embrace and extend -- although I do see desktop enviroments starting to realize that apps that aren't your native toolkit/libs, still deserve a home in your desktop project. GNOME uses Netscape extensively in it's desktop -- yet I don't see the anybody trying to lock you into a particuluar piece of software -- but more like allowing you to use more apps with your desktop enviroment of choice.
It's hasn't started with KDE 2.0. Ever since KDE 1.1 and later KDE teams have been creating ways for non-KDE apps to work better with KDE, such as using cross-theming (to at least try to match widgit colors the best as possible). Currently that supports apps using tk's gui librarys (wish), Netscape, Motif apps, and athoen widgits. So basically every Linux X11 app (excluding those written in gtk+) is color themed automatically by KDE 1.1.x (if you choose the cross-theming option in kcontrol). This is a good thing. It for one makes applications look / feel more consistant, and finally it makes those nice themes look even nicer.
And yes, KDE 2.0 will include tools for converting KDE widgit themes to GTK+ and vise-versa. Mosfet is currently working on this feature, along with the KDE widgit theme designer (finally fast, and useful themes).
I am not sure if GNOME will support similar features in the 2.0 release, but I sure hope they will -- It just makes Linux feel so much more intergrated and useful, even if it's real benfit is little.
As for other standards, both the GNOME and KDE parties are working togther. Both sides are working hard to choose the same audio server for compatiblity between various apps. The same can be said about window manger hints -- both want to use the same set of hints, which should be fully documented as part of the Window Manger Spec 2.0. So any Window Manger compatible with Window Manger Spec 2.0 should be able to work fully with both desktop enviroments, and settings for the window manger should be fully embedable in the main control panel of the desktop enviroment. Finally, for release 2.0, both desktop enviroments have agreed on a common drag and drop protocol -- xdnd.
Well... that's how it's suppost to work in theroy. Lets hope it does.
Newer Macintoshes have decent openfirmware, that support a good portion of the OpenFirmware standard, and of course output to the screen.
Only the oldest PCI-PowerMacs can't do Open Firmware display to the screen -- since that version was buggy, developmental and barely usable compared to the standard.
He was right, pretty much. All of KDE is avalible under the library/lesser gnu public license (LGPL), except for one special part (the widgits set) which is under a particuluar license depending on the version.
Summary:
Free Edition, qt 1.x - Distributable in Source / Binary forms as long as you didn't change it or use it to develop closed source programs. X11-only.
Free Edition, qt 2.x - Distributable in Source / Binary forms, you can change it / patch it, but be aware that you may not change legal info or claim that your patches are part of the offical distro. You may develop any open source program using it (on X11 only), but developing closed programs is prohibted without a special license.
KDE 1.x / KDE 2.x - All avalible under the LGPL, although some of the additional apps are GPL-only.
Re:..and it fixes that gradient bug
on
KDE 1.1.2 is out
·
· Score: 1
Yes... actually that bug has been fixed for quite (via. an additional patch) a while -- but it's not been part of the offical KDE distro until 1.1.2.
There were even some 1.1.1 PPC.RPMs around the net that had that patch... but they weren't standard and didn't ship with any of the populuar PowerPC Linux distros.
AFAIK, all known PowerPC issues are patched in KDE 1.1.2, except for the.wav bug.
It's a 15 meg download, and like the 1.1.2 source distro all of the major PowerPC patches have been merged into the KDE main source tree so KDE 1.1.2 should work good / reilably for you.
Thank Franzo. He really got a jump on this release -- even before the RedHat binaries.
PS: I am also getting KDE 1.1.2 for PowerPC Linux now.:)
Yes, the would suck for minors -- for many reasons:
1) One is that it would actually make it more appealing for minors (let's light a few reffers up in the back room so we can break the law!) [Admit it: you have been in a party like this]
2) What's wrong with a minor lighting up a cigrate once and a while -- most kids over 6 are confident enough to know that cigrates are dangerous, and could kill you. And if you don't smoke that often, what's the big deal. The same thing applies to beer -- almost everybody under 21 has had a glass at a party or somewheres -- eventhough it was illegal.
And how often can this laws be enfourced -- everybody knows at least one person that has been stoned a few times in their lives -- and they haven't been arrested (and if you don't take a look at the famous Beatle's porch picture of them smoking a reffer or the picture of Donvan without clothes on smoking one.)
And AFAIK they have not been arrested or fined.
Re:Firewire is much more advanced than USB
on
Is firewire dying?
·
· Score: 1
25 cents a system is pretty pricey for that $20 CD player -- or even a $100 stereo system -- companies budgets are tight -- and 25 cents can make a real difference.
Plus 25 cents a system adds up fast -- 1000 systems will cost a company $250 bucks, 10000 systems will cost $2,5000 dollars.
Apple is the only major vendor that ever fully supported RS-422, and they supported it for 15 years on their Macintosh platform -- from 1983 to 1998.
RS-422 was populuar because it was fairly backwards comaptible with RS-232, but it never became a hit in other markets -- for the reasons you stated -- how many people on x86 boxes used serial ports for networking.
The main reason Macintosh-pre-1999 used RS-422, was because it relied on RS-422 for it's cabling standard for small slow networks -- and it was built in to every Macintosh.
RS-422 worked good for AppleTalk, but over the years, the speed of AppleTalk became slower and slow until it was obsolete -- and Apple decided to drop this bus for the more populuar and faster 100-tbase Ethernet.
Personally, I have to agree Firewire has some serious issues -- with licensing and limitations (like Firewire doesn't work well with long distances).
Apple (and other companies) may have been working to create the world's future bus that everything would be hooked to in the future -- but because of various problems with Firewire, it might not become the 'one'.
Having a universal bus would be great, but to make this standard it would have to be the following:
- Fast Enough for Multiple Streams of 5-channel uncompressed audio, plus DVD or better quality video. - Support Large Networks. - Be an open standard. - Support Peer to Peer Connections - Be Simple enough that cheap hardware could support it. - Work with all populuar Audio, video, and Computer gear. - Support peer to peer communications.
Right now, we rely on all kinds of incompatible Buses to do this -- and I see this to continue in the future. (Think, Serial, Parrel, SCSI, RGB, SVGA, Firewire, USB, S-Video, Phono Cables, IDE/ATA, and let's not forget half a dozen other properity connector's like SWIM3.)
And, I don't see this to change. Let's look at the Phono Plug -- introduced in 1947 (yes, 52 years ago!) and it's still standard on virtually all audio gear. Even though the Phonograph is becoming rarer -- we still use it.
And yes, the Phono Plug was properity -- it was invented by RCA corpration -- but at least they were very libral about licensing it (anybody could use it for nothing) -- so it became a standard.
And the RCA phono plug has continued with time -- we now use it to send analog data from CD Players, 33 1/3 LP records, Tape Decks, Computer Audio -- all never even dreamed of in 1947.
I am sure, 20 years from now the phono-plug will still the standard for analog audio!
Yes, that is very true -- and here is some proof that Firewire is here to stay:
- October Sound and Vision Mag -- (http://www.soundandvisionmag.com) -- a glimpse into the future of digital audio / video.
It basically talks some about how firewire in the future will replace those good ole' phono cables, for all but the cheapest hi-fi systemes and speaker wires. The benifits are obvious -- especially if all stereo gear agrees on a open protocol -- you get 5 channel sound, running through all of your pherials daisy chained. That would make setting up a stereo sooo much easier, computer hi-fi audio would finally exist (pop that nice black PC above the AMP and under the EQ).
Anyway's when can I buy my Firewire phonograph -- I want one now!
Another article on why Firewire is better the USB-2.0 is at http://www.MacKiDo.com/Hardware/USB20.html That basically explains why Firewire is a better bus for high-end stuff.
At any rate, remember SCSI wasn't standard on, PC's until the mid-90's, and many PC's still use the old slow pararell port. So we will see... if Firewire continues to be hit, then good, if not, there is always USB to fall back to.
You can create Javascript based animated PNGs -- and I find it works pretty good for most of the audience of my site. Most people that have support for PNG images in there browser also support Javascript.
I really don't mind Javascript-animations -- they aren't as resource intensive as Java (or take 5 minutes to load) and are pretty easy to code.
Finally, Javascript animations are far more flexable then what GIF supports or motion PNG/JPEG images.
"I would also be cool if apple or moto or ibm would pay to get gcc up and optimized on linux-powerpc specifically."
Well, at least Motorola has contributed dozens of various patches to the Linux/PPC effort -- including some to egcs/gcc -- for better PowerPC support now and for future support of Altivec processors.
While, I don't think Motorola has full time programmers working on patching / improving PowerPC-Linux, I do know for a fact that they have people, at least part time / free time / slacking of from work time, working on getting Linux supported better on the PowerPC, and better on hardware they ship. They made Linux/PPC on CHRP possible, and helped get it on there embeded systems.
Many of Motorola employees, would love the day they can get Windows NT boxes off there desks -- many which run on Intel machines (which you can see why Motorola employees dislike there Intel Window NT boxes).
Don't believe me -- check the Linux/PPC Mailing Lists (for old patches) or the Motorola Computing group Linux website.
Even if they did code to check to make sure for Apple hardware -- people would figure how to get around it -- using methods like recycling ROMs from first generation G3s and soldering them on to daughter board for CHRP boxes -- and using some kind of OpenFirmware hack to get around them. Or maybe just keep a software image in memory -- illegal yes -- but people would try it (remember the Mac-clones of early 1980's.)
And there might be extentions that crack Mac OS X so it doesn't do this check or that it lie to Mac OS X about the installed hardware.
If there is an challenge, crackers will often break it quickly -- no matter how hard / well Apple designs it.
You are seeing more stuffing making it to PowerPC Linux everyday -- it's not a difficult port from one Linux to another -- and it's a cheap way to sell more copies of product -- with mimual testing / support.
Stuff that is here now or is being promised:
- Netscape Communicator 4.6.1 is here now.
- Applixware (latest version) for glibc 2.1 is being ported. The last version for glibc 1.99 is out.
- CTP/Civilization is out and bunch of other commerical Linux games are being ported, including Riven (yes!).
- IBM DB/2 Database software is avalible for Linux/PPC.
- JDK 1.2 is out today.
- Adobe Acrobat Reader 4.0 is Comming Soon.
- SheepShaver 2.1 for running Mac OS apps is almost ready for release.
- RealPlayer G2 for Linux/PPC is under study of Real Inc., to see if such a port would be worth while -- figuring how much the Mac OS port of RealPlayer G2 sucks, people would really love a solid Linux/PPC version of this.
- BOCH (in.ppc.rpm format) for Linux/PPC glibc 2.1. Run great PC x86 software on your Linux/PPC including Windows.
- And a bunch others that I can't yet think of.
And yes there is all of that great GNU software out there for the PowerPC including:
- KDE / GNOME desktop enviroments. - XFree86/XF68_FBDev X Server - Mac-On-Linux. Run Mac OS or extra copy of Linux/PPC or MkLinux in a seprate console -- this is great stuff. - KOffice/AbiWord/Gnumeric/GIMP/Apache and many, many other great ones.
So you aren't by far limited on Linux/PPC -- you'll find yourself with lots of great software. And great friendly user base and friendly developers.
Lets not forget Apple helped design CHRP (and is currently selling CHRP-like Macs -- Blue G3 / iBook come to mind).
So plug and play works without problems, no matter what OS use choose on the PowerPC -- Plug in that SCSI hard drive -- and mount it in Linux -- no fidling at all. Plug in that ethernet card in a PCI slot -- make sure you have the correct drivers compiled into the kernel -- and your ready to rock.
Linux is much easier to set up on the PowerPC -- inheritably due to the much better hardware design -- doesn't matter if it's PowerMac, CHRP or RS/6000.
PowerPC hardware is designed to make adding hardware as easy and do-able as possible -- it doesn't matter of the OS.
umm... Linux/PPC couldn't care about if you have an ROM or not your machine -- it never reads it at all -- neither does OpenFirmware.
The main problem with Linux on Macs is:
- They are quite expensive -- for obvious reasons -- they are brand name computers, and have licensing fees doing with the Mac OS.
- Macs traditionally have had weaker OpenFirmware compared to CHRP and IBM machines -- since OpenFirmware wasn't much of a use for Apple -- since why would an Apple machine need to select OS (besides Mac OS X vs. Mac OS Classic) or Password Protection.
- You are limited in selection when you buy an Apple machine -- CHRP gives you many more choices.
Apple is working hard to improve their weeknesses -- and it's showing up -- look at iMac -- cheap, nice looking, and a half decent OF implementation.
OpenFirmware on the Mac equals BIOS on the PC. quik on the Mac equals lilo on the PC. Linux/PPC Kernel on the Mac equal Linux/x86 Kernel on the PPC.
So it works basically the same way -- it should be noted that at least on Power Macintoshes, OpenFirmware booting has fallen out of favor of Linux/PPC developers -- so they aren't actively updating quik / Linux/PPC Kernel for better support of newer macs (blue G3/iMac) with less-brain dead OpenFirmware.
It's not that it's difficult either -- NetBSD fully supports OF booting on the iMac and the BlueG3 -- just Linux/PPC developer have no interest and continuing active development on a cryptic boot language -- when people can use something that came (free of cost -- not free as in freedom) with there PowerMac Blue/iMac G3.
Yah... But it won't work with those flashy iMacs or Blue G3's because the Linux/PPC Kernel has broken OF headers which allow it only to boot on older machines (Apple fixed part of there broken OF to make it more standard -- and Linux/PPC developers haven't kept up.)
The reason for this is, it would seem little of them have interest in wasting time to do this -- after all why bother, when the Mac OS comes free with these computers, and BootX works just as good as open firmware and is easy to use.
The fact is, people that use Linux-only Blue G3's want to be able to use OpenFirmware -- any people interested in this project?
Finally, CHRP machines boot right out of OF into Linux.
And many Mac users and some Windows users use Hotline for piracy -- it's a good place to find Mac OS and some Windows software -- not to mention a few good Mp3s.
And no, I don't recall ever downloading a file from a hotline server -- I just go there to chat or something.;-)
A fact of life, is as software become more advanced and powerful, you are eventually going to need faster hardware. Yes, forward compatiblity exists to an extent, but running Quicktime 4 on an 68020 or running a modern Linux version + X + full featured desktop + network services demands more then a i386.
UNIX is inheritably bigger, not because it's bloated -- but because it's designed to be more flexable -- since traditional UNIX hardware makes PC's look like toys -- so you do need some RAM and speed to use a modern UNIX setup completely with advanced desktop configuration.
We will try to support old machines as much as possible -- but it's not always pratical -- you can always yourself hack the code to preform better on your machine.
In the days of 450-600 mhz processor machines, with 128 megs of RAM, and the majority of users using machines around 200mhz with 32-64 megs of RAM, the OS is going to be more optimized for this hardware -- and not as much for a 16 mhz or 33 mhz machine.
Slashdot Mirror
"Tiny window 1/8 screen in size, fonts that ugly that I did not even know that they existed on my box"
Do you have your server resolution (dpi) set right. Mozilla is one of many new (like GIMP 1.2, Konsole 1.1.x) X Windows apps that require your dpi to be set right. On my X Server (Xpmac) that is done using: 'Xpmac -dpi 72' -- other X Servers do this differently. Fonts will look really large in these apps if your DPI is too high, and really small if your DPI is too low. If you are getting blocky fonts then for some reason your truetype or ghostscript fonts weren't set up right.
"buttons and widgets coming from a nightmare..."
You don't like the new XUL? Well, guess what it's really themeable. see Mozillazine for details. Some of the nightly builds (at least for Win32) have an option that caches the widgit pixmaps so they are as fast as your reguluar ones. They will be fast really soon, according to Mozillazine. :)
And yes, Netscape 4.7 works good for me (it's stable and has only minor memory leaks that all web browsers have), I am using it now -- but I would like to be able to upgrade someday.
A few things to check:
*Are you running with a frame buffer native to your card instead of the generic OpenFirmware one? That means running without using video=ofonly or No Video Driver Checked. Most Macs use atyfb, controlfb, aty128fb, or valykriefb -- most likely on a PowerBook G3 it's atyfb.
*Check out the new Xpmac and XFree86-3.3.5. Get the new Xpmac from http://khendricks.ivey.uwo.ca/rage128_us b/. Don't forget if you have a ATI Mach64 video card to start it with 'Xpmac -mach64', you will get much better preformance.
I hope those tips make your X experience better.
In my experience Xpmac -mach64 is as fast or faster then Mac OS running at 1024x768 @ thousands of colors. Then again, on my 2 meg ATI Mach64, that doesn't take much.
I have to agree with the Macintosh version of Microsoft Internet Exploiter is slow and crashy. It also has problems rendering pages that Netscape 4.5.1 (the version I run -- and prefer 'cause it's really stable) renders perfectly.
Most people I know who use Macs still prefer Netscape Communicator, and I do, because it's just a great browser. Pluse there is a PowerPC Linux version of Netscape Communicator. For us that run both PowerPC Linux and Mac OS, having the same browser and interface is a blessing.
All and All, Netscape for Macintosh rocks.
I can't comment on doing this digitally, since I haven't worked with really expensive CD-ROM drives, although ALL computer CD-ROM drives are capable of doing it the old fashion way (digital to analog to digital type setup). This isn't the best for sound quality, but in most cases it perfectly fine for everyday -- and is how most Mp3s are ripped and most CD-ROM drives. So basically the analog audio out cable of the CD-Drive hooks to a special analog input on the motherboard.
On newer PowerMacs (G4s come to mind) I have heard that this is completely digital (a PCM digital cable hooks to motherboard directly), so you don't get any sound degration at all from the decoding and reincoding and redecoding of the music.
Why they don't just use standard ATAPI or SCSI for digitally encoded sound data is beyond me. Maybe because it takes up to much bandwidth on slower buses? Or maybe because the CD player would stop playing (or play static) when you were transfering lots of data this way?
Again, I have only messed with PowerPC-based PowerMacs, so I don't know how PCs do this.
hmm... actually that's an interesting thought.
However, I don't think it's true. For one why would one desktop enviroment want to kill another one? There is no money reward.
And I have yet to find an example of embrace and extend -- although I do see desktop enviroments starting to realize that apps that aren't your native toolkit/libs, still deserve a home in your desktop project. GNOME uses Netscape extensively in it's desktop -- yet I don't see the anybody trying to lock you into a particuluar piece of software -- but more like allowing you to use more apps with your desktop enviroment of choice.
It's hasn't started with KDE 2.0. Ever since KDE 1.1 and later KDE teams have been creating ways for non-KDE apps to work better with KDE, such as using cross-theming (to at least try to match widgit colors the best as possible). Currently that supports apps using tk's gui librarys (wish), Netscape, Motif apps, and athoen widgits. So basically every Linux X11 app (excluding those written in gtk+) is color themed automatically by KDE 1.1.x (if you choose the cross-theming option in kcontrol). This is a good thing. It for one makes applications look / feel more consistant, and finally it makes those nice themes look even nicer.
And yes, KDE 2.0 will include tools for converting KDE widgit themes to GTK+ and vise-versa. Mosfet is currently working on this feature, along with the KDE widgit theme designer (finally fast, and useful themes).
I am not sure if GNOME will support similar features in the 2.0 release, but I sure hope they will -- It just makes Linux feel so much more intergrated and useful, even if it's real benfit is little.
As for other standards, both the GNOME and KDE parties are working togther. Both sides are working hard to choose the same audio server for compatiblity between various apps. The same can be said about window manger hints -- both want to use the same set of hints, which should be fully documented as part of the Window Manger Spec 2.0. So any Window Manger compatible with Window Manger Spec 2.0 should be able to work fully with both desktop enviroments, and settings for the window manger should be fully embedable in the main control panel of the desktop enviroment. Finally, for release 2.0, both desktop enviroments have agreed on a common drag and drop protocol -- xdnd.
Well... that's how it's suppost to work in theroy. Lets hope it does.
Newer Macintoshes have decent openfirmware, that support a good portion of the OpenFirmware standard, and of course output to the screen.
Only the oldest PCI-PowerMacs can't do Open Firmware display to the screen -- since that version was buggy, developmental and barely usable compared to the standard.
He was right, pretty much. All of KDE is avalible under the library/lesser gnu public license (LGPL), except for one special part (the widgits set) which is under a particuluar license depending on the version.
Summary:
Free Edition, qt 1.x - Distributable in Source / Binary forms as long as you didn't change it or use it to develop closed source programs. X11-only.
Free Edition, qt 2.x - Distributable in Source / Binary forms, you can change it / patch it, but be aware that you may not change legal info or claim that your patches are part of the offical distro. You may develop any open source program using it (on X11 only), but developing closed programs is prohibted without a special license.
KDE 1.x / KDE 2.x - All avalible under the LGPL, although some of the additional apps are GPL-only.
Yes... actually that bug has been fixed for quite (via. an additional patch) a while -- but it's not been part of the offical KDE distro until 1.1.2.
.wav bug.
There were even some 1.1.1 PPC.RPMs around the net that had that patch... but they weren't standard and didn't ship with any of the populuar PowerPC Linux distros.
AFAIK, all known PowerPC issues are patched in KDE 1.1.2, except for the
Get KDE 1.1.2 for any flavor of glibc PowerPC Linux at ftp://ftp. de.kde.org/pub/kde/stable/1.1.2/distribution/rpm/p pc/binaries/.
:)
It's a 15 meg download, and like the 1.1.2 source distro all of the major PowerPC patches have been merged into the KDE main source tree so KDE 1.1.2 should work good / reilably for you.
Thank Franzo. He really got a jump on this release -- even before the RedHat binaries.
PS: I am also getting KDE 1.1.2 for PowerPC Linux now.
Yes, the would suck for minors -- for many reasons:
1) One is that it would actually make it more appealing for minors (let's light a few reffers up in the back room so we can break the law!) [Admit it: you have been in a party like this]
2) What's wrong with a minor lighting up a cigrate once and a while -- most kids over 6 are confident enough to know that cigrates are dangerous, and could kill you. And if you don't smoke that often, what's the big deal. The same thing applies to beer -- almost everybody under 21 has had a glass at a party or somewheres -- eventhough it was illegal.
And how often can this laws be enfourced -- everybody knows at least one person that has been stoned a few times in their lives -- and they haven't been arrested (and if you don't take a look at the famous Beatle's porch picture of them smoking a reffer or the picture of Donvan without clothes on smoking one.)
And AFAIK they have not been arrested or fined.
25 cents a system is pretty pricey for that $20 CD player -- or even a $100 stereo system -- companies budgets are tight -- and 25 cents can make a real difference.
Plus 25 cents a system adds up fast -- 1000 systems will cost a company $250 bucks, 10000 systems will cost $2,5000 dollars.
It's still not cheap.
Apple is the only major vendor that ever fully supported RS-422, and they supported it for 15 years on their Macintosh platform -- from 1983 to 1998.
RS-422 was populuar because it was fairly backwards comaptible with RS-232, but it never became a hit in other markets -- for the reasons you stated -- how many people on x86 boxes used serial ports for networking.
The main reason Macintosh-pre-1999 used RS-422, was because it relied on RS-422 for it's cabling standard for small slow networks -- and it was built in to every Macintosh.
RS-422 worked good for AppleTalk, but over the years, the speed of AppleTalk became slower and slow until it was obsolete -- and Apple decided to drop this bus for the more populuar and faster 100-tbase Ethernet.
Personally, I have to agree Firewire has some serious issues -- with licensing and limitations (like Firewire doesn't work well with long distances).
Apple (and other companies) may have been working to create the world's future bus that everything would be hooked to in the future -- but because of various problems with Firewire, it might not become the 'one'.
Having a universal bus would be great, but to make this standard it would have to be the following:
- Fast Enough for Multiple Streams of 5-channel uncompressed audio, plus DVD or better quality video.
- Support Large Networks.
- Be an open standard.
- Support Peer to Peer Connections
- Be Simple enough that cheap hardware could support it.
- Work with all populuar Audio, video, and Computer gear.
- Support peer to peer communications.
Right now, we rely on all kinds of incompatible Buses to do this -- and I see this to continue in the future. (Think, Serial, Parrel, SCSI, RGB, SVGA, Firewire, USB, S-Video, Phono Cables, IDE/ATA, and let's not forget half a dozen other properity connector's like SWIM3.)
And, I don't see this to change. Let's look at the Phono Plug -- introduced in 1947 (yes, 52 years ago!) and it's still standard on virtually all audio gear. Even though the Phonograph is becoming rarer -- we still use it.
And yes, the Phono Plug was properity -- it was invented by RCA corpration -- but at least they were very libral about licensing it (anybody could use it for nothing) -- so it became a standard.
And the RCA phono plug has continued with time -- we now use it to send analog data from CD Players, 33 1/3 LP records, Tape Decks, Computer Audio -- all never even dreamed of in 1947.
I am sure, 20 years from now the phono-plug will still the standard for analog audio!
Yes, that is very true -- and here is some proof that Firewire is here to stay:
- October Sound and Vision Mag -- (http://www.soundandvisionmag.com) -- a glimpse into the future of digital audio / video.
It basically talks some about how firewire in the future will replace those good ole' phono cables, for all but the cheapest hi-fi systemes and speaker wires. The benifits are obvious -- especially if all stereo gear agrees on a open protocol -- you get 5 channel sound, running through all of your pherials daisy chained. That would make setting up a stereo sooo much easier, computer hi-fi audio would finally exist (pop that nice black PC above the AMP and under the EQ).
Anyway's when can I buy my Firewire phonograph -- I want one now!
Another article on why Firewire is better the USB-2.0 is at http://www.MacKiDo.com/Hardware/USB20.html That basically explains why Firewire is a better bus for high-end stuff.
At any rate, remember SCSI wasn't standard on, PC's until the mid-90's, and many PC's still use the old slow pararell port. So we will see... if Firewire continues to be hit, then good, if not, there is always USB to fall back to.
You can create Javascript based animated PNGs -- and I find it works pretty good for most of the audience of my site. Most people that have support for PNG images in there browser also support Javascript.
I really don't mind Javascript-animations -- they aren't as resource intensive as Java (or take 5 minutes to load) and are pretty easy to code.
Finally, Javascript animations are far more flexable then what GIF supports or motion PNG/JPEG images.
"I would also be cool if apple or moto or ibm would pay to get gcc up and optimized on linux-powerpc specifically."
Well, at least Motorola has contributed dozens of various patches to the Linux/PPC effort -- including some to egcs/gcc -- for better PowerPC support now and for future support of Altivec processors.
While, I don't think Motorola has full time programmers working on patching / improving PowerPC-Linux, I do know for a fact that they have people, at least part time / free time / slacking of from work time, working on getting Linux supported better on the PowerPC, and better on hardware they ship. They made Linux/PPC on CHRP possible, and helped get it on there embeded systems.
Many of Motorola employees, would love the day they can get Windows NT boxes off there desks -- many which run on Intel machines (which you can see why Motorola employees dislike there Intel Window NT boxes).
Don't believe me -- check the Linux/PPC Mailing Lists (for old patches) or the Motorola Computing group Linux website.
Even if they did code to check to make sure for Apple hardware -- people would figure how to get around it -- using methods like recycling ROMs from first generation G3s and soldering them on to daughter board for CHRP boxes -- and using some kind of OpenFirmware hack to get around them. Or maybe just keep a software image in memory -- illegal yes -- but people would try it (remember the Mac-clones of early 1980's.)
And there might be extentions that crack Mac OS X so it doesn't do this check or that it lie to Mac OS X about the installed hardware.
If there is an challenge, crackers will often break it quickly -- no matter how hard / well Apple designs it.
You are seeing more stuffing making it to PowerPC Linux everyday -- it's not a difficult port from one Linux to another -- and it's a cheap way to sell more copies of product -- with mimual testing / support.
.ppc.rpm format) for Linux/PPC glibc 2.1. Run great PC x86 software on your Linux/PPC including Windows.
Stuff that is here now or is being promised:
- Netscape Communicator 4.6.1 is here now.
- Applixware (latest version) for glibc 2.1 is being ported. The last version for glibc 1.99 is out.
- CTP/Civilization is out and bunch of other commerical Linux games are being ported, including Riven (yes!).
- IBM DB/2 Database software is avalible for Linux/PPC.
- JDK 1.2 is out today.
- Adobe Acrobat Reader 4.0 is Comming Soon.
- SheepShaver 2.1 for running Mac OS apps is almost ready for release.
- RealPlayer G2 for Linux/PPC is under study of Real Inc., to see if such a port would be worth while -- figuring how much the Mac OS port of RealPlayer G2 sucks, people would really love a solid Linux/PPC version of this.
- BOCH (in
- And a bunch others that I can't yet think of.
And yes there is all of that great GNU software out there for the PowerPC including:
- KDE / GNOME desktop enviroments.
- XFree86/XF68_FBDev X Server
- Mac-On-Linux. Run Mac OS or extra copy of Linux/PPC or MkLinux in a seprate console -- this is great stuff.
- KOffice/AbiWord/Gnumeric/GIMP/Apache and many, many other great ones.
So you aren't by far limited on Linux/PPC -- you'll find yourself with lots of great software. And great friendly user base and friendly developers.
Lets not forget Apple helped design CHRP (and is currently selling CHRP-like Macs -- Blue G3 / iBook come to mind).
So plug and play works without problems, no matter what OS use choose on the PowerPC -- Plug in that SCSI hard drive -- and mount it in Linux -- no fidling at all. Plug in that ethernet card in a PCI slot -- make sure you have the correct drivers compiled into the kernel -- and your ready to rock.
Linux is much easier to set up on the PowerPC -- inheritably due to the much better hardware design -- doesn't matter if it's PowerMac, CHRP or RS/6000.
PowerPC hardware is designed to make adding hardware as easy and do-able as possible -- it doesn't matter of the OS.
umm... Linux/PPC couldn't care about if you have an ROM or not your machine -- it never reads it at all -- neither does OpenFirmware.
The main problem with Linux on Macs is:
- They are quite expensive -- for obvious reasons -- they are brand name computers, and have licensing fees doing with the Mac OS.
- Macs traditionally have had weaker OpenFirmware compared to CHRP and IBM machines -- since OpenFirmware wasn't much of a use for Apple -- since why would an Apple machine need to select OS (besides Mac OS X vs. Mac OS Classic) or Password Protection.
- You are limited in selection when you buy an Apple machine -- CHRP gives you many more choices.
Apple is working hard to improve their weeknesses -- and it's showing up -- look at iMac -- cheap, nice looking, and a half decent OF implementation.
OpenFirmware on the Mac equals BIOS on the PC.
quik on the Mac equals lilo on the PC.
Linux/PPC Kernel on the Mac equal Linux/x86 Kernel on the PPC.
So it works basically the same way -- it should be noted that at least on Power Macintoshes, OpenFirmware booting has fallen out of favor of Linux/PPC developers -- so they aren't actively updating quik / Linux/PPC Kernel for better support of newer macs (blue G3/iMac) with less-brain dead OpenFirmware.
It's not that it's difficult either -- NetBSD fully supports OF booting on the iMac and the BlueG3 -- just Linux/PPC developer have no interest and continuing active development on a cryptic boot language -- when people can use something that came (free of cost -- not free as in freedom) with there PowerMac Blue/iMac G3.
Yah... But it won't work with those flashy iMacs or Blue G3's because the Linux/PPC Kernel has broken OF headers which allow it only to boot on older machines (Apple fixed part of there broken OF to make it more standard -- and Linux/PPC developers haven't kept up.)
The reason for this is, it would seem little of them have interest in wasting time to do this -- after all why bother, when the Mac OS comes free with these computers, and BootX works just as good as open firmware and is easy to use.
The fact is, people that use Linux-only Blue G3's want to be able to use OpenFirmware -- any people interested in this project?
Finally, CHRP machines boot right out of OF into Linux.
And many Mac users and some Windows users use Hotline for piracy -- it's a good place to find Mac OS and some Windows software -- not to mention a few good Mp3s.
;-)
And no, I don't recall ever downloading a file from a hotline server -- I just go there to chat or something.
A fact of life, is as software become more advanced and powerful, you are eventually going to need faster hardware. Yes, forward compatiblity exists to an extent, but running Quicktime 4 on an 68020 or running a modern Linux version + X + full featured desktop + network services demands more then a i386.
UNIX is inheritably bigger, not because it's bloated -- but because it's designed to be more flexable -- since traditional UNIX hardware makes PC's look like toys -- so you do need some RAM and speed to use a modern UNIX setup completely with advanced desktop configuration.
We will try to support old machines as much as possible -- but it's not always pratical -- you can always yourself hack the code to preform better on your machine.
In the days of 450-600 mhz processor machines, with 128 megs of RAM, and the majority of users using machines around 200mhz with 32-64 megs of RAM, the OS is going to be more optimized for this hardware -- and not as much for a 16 mhz or 33 mhz machine.