I'm sorry that your experience with linux has thus far been so bad. I understand how frustrating dealing with linux and all these problems might be. The linux community as a whole is very willing to help, but there are lots of questions that are commonly asked that are answered in howto and mailing archives.
many people who use linux and read these mailing list are busy people, though willing to help, are probably like you, with lots of commitments. they usually have little amount of time that they need to delegate constructively. you'll get much friendlier responses if you would do your homework beforehand by: (1) reading the relavent howto's (2) browse/search the mailing list archives for previous posts that are relevant. now, though i'm no guru (far from it), let's get on to your questions =) (1) it helps a LOT if you know we know what network card it is. also the chipset the card uses. you usually needs these in order to determine the correct drivers. i like to check /proc/pci to see if the card was detected at startup. if it is, then you just need to install the drivers. installing the drivers can be done from modconf (again, i'm not sure of the program, i don't use it =p ). you can also compile your own kernel and put the drivers in that way. read the kernel-howto. =) (2) though i haven't setup a two network card system before i believe the idea is the same. you would use ifconfig eth0 ... the same arguments you give to the first card except changing eth0 to the device file your second card is on (probably eth1). these are usually done at boot in a script: /etc/init.d/networking (/etc/init.d/network in slink). though they've been changing that around on me. =p please read the howto's and mailing list archives first. then post the question. you'll find more people are willing to help you. Herbert Ho On Fri, 8 Oct 1999 [EMAIL PROTECTED] wrote: > I was under the _impression_ that people in the Linux community were > supposed to be helpful. Obviously I was mistaken. > > I asked some very specific questions, I hoped to get some helpful > answers. Obviously I was mistaken to even bother if I was to simply be > directed to a Howto file. > > The poor quality of documentation, such as these "how tos" is one of the > reasons why I recommend when ever I am asked whether a site should move > to linux to recommend that they don't. They are far better off with a > proprietory WELL SUPPORTED form of unix, even if it costs considerably > more. That way they won't get a smart arse answer like this when they > ask a direct question. > > I don't want a long, indepth, very indirect discussion of how to manage > a network or ethernet connect. I want clear, distinct EXAMPLES. > > Now, little boy, pull your socks up. If you're not willing to help then > it might be better for you to remain silent, rather than remove any > doubt in my mind that you're a fool. > > > > Take a look at the Ethernet and NETWORK HOWTOs. > > > > > I have a system on which I've just installed debian. It has two network > > > cards but during setup only one was recognised. I need to know how to: > > > > > > 1) Make the system recognise the other network card. Is there a utility > > > which probes the card and determines what type it is and (hopefully) > > > installs the correct driver for it? > > > > > > 2) Make the system utilise the other network card. > > > > > > 3) How do I assign a seperate IP number, gateway, etc. to it? > > > > > > > > > > > > cheers > > > > > > Brian > > > > > > > > > -- > > > Brian Ross, Network Manager Voice +61-1-2-6279-8336 > > > John Curtin School of Medical Research Fax +61-1-2-6247-4823 > > > Australian National University > > > > > > > > > -- > > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- > Brian Ross, Network Manager Voice +61-1-2-6279-8336 > John Curtin School of Medical Research Fax +61-1-2-6247-4823 > Australian National University > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
