You should not package an OpenOffice with an unscalale "Times"-Font and other completely unusable Fonts. This turns off newbies and people how are just interested in Linux. -snip-
Make sure that _every_ font in the system renders and works perfectly out of the box in OpenOffice, Mozilla and Printing!!
Yeah, because every font in Windows/MS Office is beautiful...
"Firefox" will do an I'm Feeling Lucky search if you type in something it thinks isn't a URL. Type in, say, "slashdot" and Firefox will do an I'm Feeling Lucky search becuase it isn't a URL. Type in, www.dsfgsdfjghk.com and it will give an not found error because www.dsfgsdfjghk.com is a URL.
Imagine the coldest thing you have ever touched. Now imagine something several hunderd times colder. So cold that the moment you touched it your hand would instantly freeze, causing all the cells in your hand to die, thus requiring it to be amputated. It probably wouldn't hurt all that much, since the nerves in your hand would be dead, but somehow it still doesn't seem to appealing.
Or who invented the supreme uber-god of all three-finger-salutes, Alt-SysRq-B?
(For those who don't know, Alt-SysRq-B instantly reboots your Linux system. It is roughly the same as hitting the reset button on your box. So be sure to precede it with Alt-SysRq-S and Alt-SysRq-U to prevent filesystem damage.)
How 'bout you wait till KDE 3.2 gets released and your distro supports it, instead of trolling slashdot about how hard it is to install test releases that "your grandma" would never hear of, much less ever want to install and how you don't want to read the manual?
Whoever owns/pays for the virtual world gets to make his own rules on what can and cannot be said. If you don't like 'em, you can always go to another one, or make your own. This is assuming that the game/whatever isn't locked into one server/world.
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-built binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Gentoo is a Linux distribution gaining in prominence these days. One of its big selling points is its portage system, which is often considered very similar to BSD ports. Perhaps most visibly, in that it compiles from source. That avoids a lot of the problem of binary packages. I've never used it myself, but the impressions I've gotten from information I've seen on it, and people I know who have used it, is that it's taken some good ideas from everyone, and smooshed them together. It'll be very interesting to see how it progresses and matures over the next few years. It's still much more Linux than BSD, but it may well be the closest to the BSD style of the major Linux distributions.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There are also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependencies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RP
Where are all the anti-Linux/pro-OSX zealots why cry that the command line is evil? Shouldn't you be whining now about how bad this is and how OSX isn't ready for the desktop?
Why doesn't the leaking air freeze as it comes out? Space is definietly cold enough. And as the leeking are freezes (as I think it does), why doesn't it plug the hole?
Obviously, a church doesn't promise anything in return. If a televangelism guy was to promise returns such as the guy doing the Nigeria scam, it WOULD be a scam. And he would got into trouble for it.
Sheesh, you people will do anything to make Christains look bad, won't you?
They only have to provide the source to you if they give you binaries. The GPL doesn't state that if I make changes to the source I must give the source to everybody. It states that if I make changes to the source and give it to anybody, I must be give _them_ the source, and all the rights of the GPL.
Simple. Themes are complete changes of look. They change everything form desktop background to widget style. Syles, on the other hand, merely change that appearance of widgets. They don't even change the color of widgets, just how they look.
Um, SuSE used KDE. And will continure using KDE (this has been pubically stated by Novell people). Mandrake's default is KDE. And I head that Debian is focusing on KDE more and more.
Whoops... there I go again, feeding the GNOME trolls.
Well, I find this screenshot really interesting.
Don't you think that Gnumeric is more "easy " than Kspread ? There's two rows of icons in Gnumeric : File icons and actions icons.
In Kspread is not so easy, you have icons anywhere.. that's really the bad point of KDE for me and why I prefer Gnome for beginners. Think about it.
Um, I see about 45 icons in Kspread and 48 in Gnumeric. I also see a nice seperator between the different toolbars. And I see icons in more seperate places in Gnumeric than in Kspread.
Slashdot Mirror
When I do that I just get a Not found error...
But I do agree with you that that should definitely be a GUI pref (and I don't mean about:config).
"Firefox" will do an I'm Feeling Lucky search if you type in something it thinks isn't a URL. Type in, say, "slashdot" and Firefox will do an I'm Feeling Lucky search becuase it isn't a URL. Type in, www.dsfgsdfjghk.com and it will give an not found error because www.dsfgsdfjghk.com is a URL.
Hooray, now I can watch their movies
;)
You could before!
Linux: aMule
Windows: eMule
And if you feel guilty, just send a couple of dollars to the Pixar guys...
Imagine the coldest thing you have ever touched. Now imagine something several hunderd times colder. So cold that the moment you touched it your hand would instantly freeze, causing all the cells in your hand to die, thus requiring it to be amputated. It probably wouldn't hurt all that much, since the nerves in your hand would be dead, but somehow it still doesn't seem to appealing.
Or who invented the supreme uber-god of all three-finger-salutes, Alt-SysRq-B?
(For those who don't know, Alt-SysRq-B instantly reboots your Linux system. It is roughly the same as hitting the reset button on your box. So be sure to precede it with Alt-SysRq-S and Alt-SysRq-U to prevent filesystem damage.)
People are trying to do just that: http://kde-cygwin.sourceforge.net/
How 'bout you wait till KDE 3.2 gets released and your distro supports it, instead of trolling slashdot about how hard it is to install test releases that "your grandma" would never hear of, much less ever want to install and how you don't want to read the manual?
Whoever owns/pays for the virtual world gets to make his own rules on what can and cannot be said. If you don't like 'em, you can always go to another one, or make your own. This is assuming that the game/whatever isn't locked into one server/world.
Since no one "owns" the real world...
It depends. Do they use Vi or *shudder*Emacs?
The Ports System
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-built binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Gentoo is a Linux distribution gaining in prominence these days. One of its big selling points is its portage system, which is often considered very similar to BSD ports. Perhaps most visibly, in that it compiles from source. That avoids a lot of the problem of binary packages. I've never used it myself, but the impressions I've gotten from information I've seen on it, and people I know who have used it, is that it's taken some good ideas from everyone, and smooshed them together. It'll be very interesting to see how it progresses and matures over the next few years. It's still much more Linux than BSD, but it may well be the closest to the BSD style of the major Linux distributions.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There are also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependencies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RP
Or another one:
What's the difference between a dead snake on the road and a dead lawyer on the road?
The dead snake has skid marks in front of it.
Where are all the anti-Linux/pro-OSX zealots why cry that the command line is evil? Shouldn't you be whining now about how bad this is and how OSX isn't ready for the desktop?
How does litigious bastards sound?
Why doesn't the leaking air freeze as it comes out? Space is definietly cold enough. And as the leeking are freezes (as I think it does), why doesn't it plug the hole?
Anyone care to enlighten me on why that is?
Except that 2.5 != 2...
...then the US constitution is Mach.
Other than the fact that that Mach sucks but the US Constitution does not... yeah.
Obviously, a church doesn't promise anything in return. If a televangelism guy was to promise returns such as the guy doing the Nigeria scam, it WOULD be a scam. And he would got into trouble for it.
Sheesh, you people will do anything to make Christains look bad, won't you?
How 'bout HTML+CSS?
They only have to provide the source to you if they give you binaries. The GPL doesn't state that if I make changes to the source I must give the source to everybody. It states that if I make changes to the source and give it to anybody, I must be give _them_ the source, and all the rights of the GPL.
Simple. Themes are complete changes of look. They change everything form desktop background to widget style. Syles, on the other hand, merely change that appearance of widgets. They don't even change the color of widgets, just how they look.
Um, SuSE used KDE. And will continure using KDE (this has been pubically stated by Novell people). Mandrake's default is KDE. And I head that Debian is focusing on KDE more and more.
Whoops... there I go again, feeding the GNOME trolls.
Konqueror can be removed. Easily.
Can you do that with IE?