Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I get what your trying to say... but Ive used DOS all my life
so when i switched to linux suse at least i understood how to use bash i mean ls and dir/w rm and del are then same so it was easy for me to adapt then i got used to suse but i was sick of buying there distros at huge prices ... so now im trying slackware
and theres noticeible changes ... lol I dont even know where i am I know how to compile programs etc but the system configureation is a little bit differnt ....and I wanna aplogize for being ignorent I usally very clam about these things.
I'm surprised anybody can reply to the original thread. It's hard when you have to translate English into English. Maybe the educational system, in their quest to make everybody happy, has deemed this sort of mix and match of words, missing apostrophes in contractions, misspellings, and misplaced ellipsis to be acceptable.
Sorry, but somebody has to try and keep effective communications going in a public forum like this.
Here's another example:
at least i understood how to use bash i mean ls and dir/w rm and del are then same
And I really don't think I am being pedantic here. I don't necessarily call for strict adherence to the rules, just some adherence.
Originally posted by CryptDragoon 3DFX is no longer in bussness so I don't think they would support new drivers since Glide went open source.
Your card should be supported as it should use the 3dfx drivers or are they called voodoo... that come with XFree86.. It was supported in Slackware 8.0 and up... so I'm sure the support is still there in the latest version.
Correct me if I am wrong, but as long as Free X86 Supports and DRI supports the hardware shouldn't it run under any distro? I mean it's not in the disto's hands to say witch cards are supported .. the kernel has some say but then there are modules that can be loaded to add support to the kernel if it doesn't support the device itself, so it really depends on FreeX86 and DRI doesn't it ?
Last edited by CryptDragoon; 10-08-2003 at 02:07 PM.
Originally posted by CryptDragoon Correct me if I am wrong, but as long as Free X86 Supports and DRI supports the hardware shouldn't it run under any distro? I mean it's not in the disto's hands to say witch cards are supported .. the kernel has some say but then there are modules that can be loaded to add support to the kernel if it doesn't support the device itself, so it really depends on FreeX86 and DRI doesn't it ?
Yes, if you have a)right kernel module compiled (or driver compiled into the kernel) b) XFree part of the driver
The thing is that the default kernel may have the drivers or not (usually it has, if it's popular hardware). Plus, there are drivers released under different licences, what may cause the driver not be included into the kernel tree and distros.
OK....I've read and kept my mouth silent.
With some restraint I offer this bit of advice....
I used to work in the R&D team of a major video hardware manufacturer <won't plug anyone>. No I didn't get fired, I retired 2 years ago, so think of another way to insult me when I'm done.
A team of 3 people (1 hardware engineer, 2 software engineers) took over 20 months to produce a win32 driver compatible with the 32 bit NT kernel. Mind you, the OS was already written, and documented. We also used assembly language, C++ with prebuilt win32 modules, C, even VB was used for the Install GUI.
This was not the first project of this type that this group undertook. So if a small group of highly experienced individuals needs over a year to produce just the DRIVER.......well you fill in the rest