Operating Systems > Linux and UNIX
The revolution begins...
WMD:
No, the Savage Pro is an old card. My dad has one he got in 2000. That's pretty old.
hm_murdock:
quote:Ok, we will have to agree to disagree on this one. If this OS is going to be as good as you say it is more RAM might be worth the money, but I hope you're not going to expect me to upgrade every year, just to run the latest version.
--- End quote ---
No modern desktop OS is happy in less than 256. Most of them today want 512. Just live with this and get 512.
quote:Exactly, when all is well, and you just want to install some hardware or software the command line shouldn't be needed. But if somthing goes wrong with KDE, say an essential file get fucked up, you should be able to boot into text mode command line and be able to fix the problem.
--- End quote ---
Okay, so the way it is. Great. Just to let you know, that's already the way things are.
quote:Windows 3.11 used protected mode for many reasons, apart from disk buffers and Win32s, but like you said, I think we're talking about completely differant uses of protected mode in Win3.1 FUCK WINDOWS you're right this isn't the place to talk about Fucking Windows but NT4 kicked Win95Bs arse! If hard drive Fucks up Recovery console should be at least allow you to back up your files!
Oh sorry, I promise to shut up about Windows now.
--- End quote ---
Sure
quote:That's good [Thumbs Up]
--- End quote ---
Yep.
quote:That's not so good.
--- End quote ---
Sure it is. Nearly everybody has a GeForce or Radeon vid card, or a major-chipset mobo, or whatever. You trade the ability to use any shitty ass no-name piece of hardware, for guaranteed stability. Once you get beyond "tested and confirmed" hardware, then you've still got a damn good chance of it working well, because Linux has great hardware support.
quote:So I would be right in asuming that if your hardware isn't "Officially supported" you will have install it the usual long winded Linux way, oh well that's not too bad I suppose.
--- End quote ---
No. If it's not officially supported, then it uses regular built-in drivers if they exist. By "Officially supported"... this means hardware that we have seen work. Stuff that has been tested and we can assure you will function right out of the box.
quote:That sounds like more bloat to me, unless it has a useful purpose other than to look pretty.
--- End quote ---
Then you don't know what bloat is, sucka. Sounds to me like a feature that every OS is supporting because even hardware from 02 works great with it. That S3 video IS SLOW AND SHITTY. Why the Hell do you try to act like it isn't? Damn dude, get with the rest of the world.
Get yourself more RAM, and a non shitty vid card. Trust me, you'll enjoy your computer a whole helluva lot more.
savet:
quote:
The command line user interface should have long gone, GUIs are the future. A GUI doesn't need to be big a resource hog, it is possible to design a very good GUI that uses up way less than 1MB of memory.
The command line should just be there to fall back on in case the GUI fails. Text based operating systems are still good for file servers and batch data processing systems, but they are useless for any process that requires a lot of human intervention.
--- End quote ---
First, do you want the command line to stay or go? These two paragraphs contradict each other, even though they both show distaste for the command line.
Second, I don't think you realize the power and versatility of the command line. Let's look at two different scenarios:
1. I'm designing a website, and I need to create directories in my websites folder. I can either open konqueror or nautilus and right click, create folder, type the name new_website_1, double click the folder, right click, select new folder, type images, right click, select new folder, type data, and repeat this slow tedious process until my entire directory structure is complete.
Now, let's look at this option with the command line.
mkdir new_website_1 && cd new_website_1 && mkdir images data
Obviously the command line is the better option here. Let's look at another one:
2. I want to install new software. I can either run a program that formats all of the output from the configure/make/make install and directs it to a graphical program with nice pretty borders, making the output text nearly impossible to copy in case I have a problem or need to reference it later. I should also mention that the resources needed to reformat the text and make it look pretty are wasted, and could be used to build the program faster.
An install from the command line not only saves resources, but you can direct the output into a log file. For example:
./configure > configure_log
make > make_log
make install > install_log
You will be able to reference the entire installation and be able to find solutions to any dependency problems much easier, not to mention have a hard copy of where everything was installed.
The command line is obviously far from obsolete
billy_gates:
oooh I can't wait
thanks for all your work will
I have done basically nothing
been wrapped up in life
sorry about that
I can't wait to see
Refalm:
quote:jeffberg: Mac Capitalist: Tired of the MES?
--- End quote ---
No sorry, MES is great ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version